@toa.io/extensions.exposition 1.0.0-alpha.284 → 1.0.0-alpha.285

package/CHANGELOG.md

@@ -3,6 +3,17 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# [1.0.0-alpha.285](https://github.com/toa-io/toa/compare/v1.0.0-alpha.284...v1.0.0-alpha.285) (2026-09-05)
+
+### Bug Fixes
+
+* **exposition:** a procedure is named in characters a tool's name may hold ([857ff75](https://github.com/toa-io/toa/commit/857ff75858e633682d5c245eccde3dc00797ec00))
+
+### Features
+
+* **exposition:** a tool says what to call it, beside what it is ([c94dcd1](https://github.com/toa-io/toa/commit/c94dcd10ab5a2875975fdba94b37dae128f454c4))
+
+
 # [1.0.0-alpha.284](https://github.com/toa-io/toa/compare/v1.0.0-alpha.283...v1.0.0-alpha.284) (2026-09-05)
 
 ### Bug Fixes

package/documentation/mcp.md

@@ -37,7 +37,9 @@ A tool is an RTD method that says it is one, named as the [procedure](rpc.md#the
   /hot:
     GET:
       query: { criteria: temperature=gt=80 }
-      mcp:tool: The pots that are too hot to pour.
+      mcp:tool:
+        title: Hot pots
+        description: The pots that are too hot to pour.
       endpoint: enumerate
 ```
 
@@ -48,6 +50,10 @@ it would spend a model's context on what it has no business calling.
 The value is what the tool is, and stating it is what publishes it — there is no way to publish one
 that says nothing, because a tool a model cannot read the purpose of is one it cannot choose.
 
+A `title` is what a person is shown where a client lists what it may call. Without one a client has
+only the name, which is an address — `apps._identity._id.repos.POST` — and reads as one. A
+description alone is written as the value; a title beside it is written as a mapping.
+
 An operation [states what it is](/documentation/component/declaration.md) as well, and that is not
 this: it is written without knowledge of any route, and a tool is an operation and a route together.
 The two routes above are one operation and two tools, and one sentence is not true of both. The

package/documentation/rpc.md

@@ -13,27 +13,31 @@ one an application could choose is one it could collide with a route of its own.
 
 ## The name
 
-A procedure is an RTD method — a node and a verb — and its name is written the way the node is
-declared: the route template, with a variable marked by a leading `_`, and the verb as the last
-segment.
+A procedure is an RTD method — a node and a verb — and its name is the route template with a
+variable marked by a leading `_` and the verb as the last segment, joined by `.`.
+
+The separator is `.` and not `/` because a name is a tool's name too, and
+[MCP](mcp.md) names the characters one may hold: letters, digits, `_`, `-` and `.`. A client that
+receives one outside that set may refuse the tool, and one that accepts it rewrites what it shows
+a model — so what is published has to be spellable as it stands.
 
 | route | verb | method |
 | --- | --- | --- |
-| `/pots` | `GET` | `pots/GET` |
-| `/pots` | `POST` | `pots/POST` |
-| `/pots/:id` | `GET` | `pots/_id/GET` |
-| `/identity/tokens/:identity` | `POST` | `identity/tokens/_identity/POST` |
-| `/files/**` | `GET` | `files/__/GET` |
+| `/pots` | `GET` | `pots.GET` |
+| `/pots` | `POST` | `pots.POST` |
+| `/pots/:id` | `GET` | `pots._id.GET` |
+| `/identity/tokens/:identity` | `POST` | `identity.tokens._identity.POST` |
+| `/files/**` | `GET` | `files.__.GET` |
 | `/` | `GET` | `GET` |
 
-The verb is always the last segment, so `/pots/GET` answering `POST` is `pots/GET/POST` and
-`/pots` answering `GET` is `pots/GET`. Nothing is declared to make a name: a re-mounted route is
+The verb is always the last segment, so `/pots/GET` answering `POST` is `pots.GET.POST` and
+`/pots` answering `GET` is `pots.GET`. Nothing is declared to make a name: a re-mounted route is
 a renamed procedure, because the name is the address.
 
 ## What has a name
 
 A segment is addressed where it holds only `A-Z`, `a-z`, `0-9` and `-`. `_` is the name's own,
-marking a variable, and `__` the rest of a path.
+marking a variable, and `__` the rest of a path; `.` is what divides one segment from the next.
 
 A route with a segment holding anything else — a `.`, a `_`, a `*`, a variable that is not one
 word — has no name. It is served over HTTP as it always was; what it loses is the address, so
@@ -51,16 +55,16 @@ A key the template names is a route variable, and is taken by the path. `query`
 querystring. Whatever is left is the body.
 
 ```json
-{"jsonrpc": "2.0", "id": 1, "method": "pots/_id/GET", "params": {"id": "a1b2"}}
+{"jsonrpc": "2.0", "id": 1, "method": "pots._id.GET", "params": {"id": "a1b2"}}
 ```
 
 ```json
-{"jsonrpc": "2.0", "id": 2, "method": "pots/POST",
+{"jsonrpc": "2.0", "id": 2, "method": "pots.POST",
  "params": {"title": "Kettle", "volume": 1.7}}
 ```
 
 ```json
-{"jsonrpc": "2.0", "id": 3, "method": "pots/GET",
+{"jsonrpc": "2.0", "id": 3, "method": "pots.GET",
  "params": {"query": {"criteria": "volume=gt=1", "limit": 10}}}
 ```
 
@@ -87,8 +91,8 @@ A request may carry an array of calls instead of one, and answers an array of wh
 answered — shorter than what it was given, where some were notifications.
 
 ```json
-[{"jsonrpc": "2.0", "id": 1, "method": "pots/_id/GET", "params": {"id": "a1b2"}},
- {"jsonrpc": "2.0", "method": "pots/_id/DELETE", "params": {"id": "c3d4"}}]
+[{"jsonrpc": "2.0", "id": 1, "method": "pots._id.GET", "params": {"id": "a1b2"}},
+ {"jsonrpc": "2.0", "method": "pots._id.DELETE", "params": {"id": "c3d4"}}]
 ```
 
 They run one after another, in the order given. `batch` is how many one request may carry, 32
@@ -127,7 +131,7 @@ in its manifest, and is what a caller reads.
 ## Authorization
 
 A procedure is authorized as the resource is, against the path and the verb its name states.
-A token restricted to `/pots/:id/` for `GET` authorizes `pots/_id/GET` and nothing else,
+A token restricted to `/pots/:id/` for `GET` authorizes `pots._id.GET` and nothing else,
 whichever way the call arrives.
 
 [`anonymous`](access.md#anonymous) is the one directive that reads a call differently from a

package/features/mcp.feature

@@ -8,7 +8,8 @@ Feature: Model Context Protocol
   says.
 
   What a tool is, is stated on the route and nowhere else. The operation states what it is
-  too, and that is not this: one operation mounted on two routes is two tools.
+  too, and that is not this: one operation mounted on two routes is two tools. A `title`
+  beside the description is what a person is shown where a client lists what it may call.
 
   Two revisions are answered from one endpoint that remembers nothing between requests: the
   modern one, where every request carries its own version and capabilities, and the one
@@ -42,7 +43,9 @@ Feature: Model Context Protocol
             GET:
               query:
                 criteria: volume>=100
-              mcp:tool: The pots that hold a hundred or more, newest first.
+              mcp:tool:
+                title: Large pots
+                description: The pots that hold a hundred or more, newest first.
               endpoint: enumerate
           /unpublished:
             GET: enumerate
@@ -160,7 +163,7 @@ Feature: Model Context Protocol
       id: 2
       result:
         tools:
-          - name: pots/GET
+          - name: pots.GET
             description: All the pots, newest first.
             inputSchema:
               type: object
@@ -178,7 +181,7 @@ Feature: Model Context Protocol
               additionalProperties: false
             annotations:
               readOnlyHint: true
-          - name: pots/POST
+          - name: pots.POST
             description: Start a new pot brewing.
             inputSchema:
               type: object
@@ -192,7 +195,7 @@ Feature: Model Context Protocol
                 - title
                 - volume
               additionalProperties: false
-          - name: pots/_id/GET
+          - name: pots._id.GET
             description: One pot, by its id.
             inputSchema:
               type: object
@@ -202,7 +205,8 @@ Feature: Model Context Protocol
               required:
                 - id
               additionalProperties: false
-          - name: pots/large/GET
+          - name: pots.large.GET
+            title: Large pots
             description: The pots that hold a hundred or more, newest first.
             annotations:
               readOnlyHint: true
@@ -212,11 +216,11 @@ Feature: Model Context Protocol
       """
     And the reply does not contain:
       """
-      pots/guarded/GET
+      pots.guarded.GET
       """
     And the reply does not contain:
       """
-      pots/unpublished/GET
+      pots.unpublished.GET
       """
     And the reply does not contain:
       """
@@ -235,10 +239,10 @@ Feature: Model Context Protocol
       content-type: application/json
       mcp-protocol-version: 2026-07-28
       mcp-method: tools/call
-      mcp-name: pots/unpublished/GET
+      mcp-name: pots.unpublished.GET
 
       {"jsonrpc": "2.0", "id": 30, "method": "tools/call",
-       "params": {"name": "pots/unpublished/GET", "arguments": {},
+       "params": {"name": "pots.unpublished.GET", "arguments": {},
                   "_meta": {"io.modelcontextprotocol/protocolVersion": "2026-07-28",
                             "io.modelcontextprotocol/clientCapabilities": {}}}}
       """
@@ -283,7 +287,7 @@ Feature: Model Context Protocol
       id: 20
       result:
         tools:
-          - name: pots/GET
+          - name: pots.GET
       """
 
   Scenario: A tool takes what the procedure takes
@@ -295,10 +299,10 @@ Feature: Model Context Protocol
       content-type: application/json
       mcp-protocol-version: 2026-07-28
       mcp-method: tools/call
-      mcp-name: pots/_id/GET
+      mcp-name: pots._id.GET
 
       {"jsonrpc": "2.0", "id": 3, "method": "tools/call",
-       "params": {"name": "pots/_id/GET",
+       "params": {"name": "pots._id.GET",
                   "arguments": {"id": "4c4759e6f9c74da989d64511df42d6f4"},
                   "_meta": {"io.modelcontextprotocol/protocolVersion": "2026-07-28",
                             "io.modelcontextprotocol/clientCapabilities": {}}}}
@@ -326,10 +330,10 @@ Feature: Model Context Protocol
       content-type: application/json
       mcp-protocol-version: 2026-07-28
       mcp-method: tools/call
-      mcp-name: pots/POST
+      mcp-name: pots.POST
 
       {"jsonrpc": "2.0", "id": 4, "method": "tools/call",
-       "params": {"name": "pots/POST", "arguments": {"title": "Kettle", "volume": 1.7},
+       "params": {"name": "pots.POST", "arguments": {"title": "Kettle", "volume": 1.7},
                   "_meta": {"io.modelcontextprotocol/protocolVersion": "2026-07-28",
                             "io.modelcontextprotocol/clientCapabilities": {}}}}
       """
@@ -354,10 +358,10 @@ Feature: Model Context Protocol
       content-type: application/json
       mcp-protocol-version: 2026-07-28
       mcp-method: tools/call
-      mcp-name: kettles/GET
+      mcp-name: kettles.GET
 
       {"jsonrpc": "2.0", "id": 5, "method": "tools/call",
-       "params": {"name": "kettles/GET", "arguments": {},
+       "params": {"name": "kettles.GET", "arguments": {},
                   "_meta": {"io.modelcontextprotocol/protocolVersion": "2026-07-28",
                             "io.modelcontextprotocol/clientCapabilities": {}}}}
       """
@@ -403,10 +407,10 @@ Feature: Model Context Protocol
       content-type: application/json
       mcp-protocol-version: 2026-07-28
       mcp-method: tools/call
-      mcp-name: pots/GET
+      mcp-name: pots.GET
 
       {"jsonrpc": "2.0", "id": 7, "method": "tools/call",
-       "params": {"name": "pots/POST", "arguments": {},
+       "params": {"name": "pots.POST", "arguments": {},
                   "_meta": {"io.modelcontextprotocol/protocolVersion": "2026-07-28",
                             "io.modelcontextprotocol/clientCapabilities": {}}}}
       """
@@ -484,7 +488,7 @@ Feature: Model Context Protocol
     named a record that is not the caller's, which it may correct itself by naming another.
     A challenge here would send the client to ask for a scope that would not help.
 
-    # developer:secret, who is not an `admin` and so may not reach `pots/guarded/GET`
+    # developer:secret, who is not an `admin` and so may not reach `pots.guarded.GET`
     Given the `identity.basic` database contains:
       | _id                              | authority | username  | password                                                     |
       | efe3a65ebbee47ed95a73edd911ea328 | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O |
@@ -498,10 +502,10 @@ Feature: Model Context Protocol
       content-type: application/json
       mcp-protocol-version: 2026-07-28
       mcp-method: tools/call
-      mcp-name: pots/guarded/GET
+      mcp-name: pots.guarded.GET
 
       {"jsonrpc": "2.0", "id": 31, "method": "tools/call",
-       "params": {"name": "pots/guarded/GET", "arguments": {},
+       "params": {"name": "pots.guarded.GET", "arguments": {},
                   "_meta": {"io.modelcontextprotocol/protocolVersion": "2026-07-28",
                             "io.modelcontextprotocol/clientCapabilities": {}}}}
       """
@@ -531,10 +535,10 @@ Feature: Model Context Protocol
       content-type: application/json
       mcp-protocol-version: 2026-07-28
       mcp-method: tools/call
-      mcp-name: pots/_id/GET
+      mcp-name: pots._id.GET
 
       {"jsonrpc": "2.0", "id": 32, "method": "tools/call",
-       "params": {"name": "pots/_id/GET",
+       "params": {"name": "pots._id.GET",
                   "arguments": {"id": "not-an-id"},
                   "_meta": {"io.modelcontextprotocol/protocolVersion": "2026-07-28",
                             "io.modelcontextprotocol/clientCapabilities": {}}}}
@@ -570,10 +574,10 @@ Feature: Model Context Protocol
       content-type: application/json
       mcp-protocol-version: 2026-07-28
       mcp-method: tools/call
-      mcp-name: echo/GET
+      mcp-name: echo.GET
 
       {"jsonrpc": "2.0", "id": 10, "method": "tools/call",
-       "params": {"name": "echo/GET", "arguments": {},
+       "params": {"name": "echo.GET", "arguments": {},
                   "_meta": {"io.modelcontextprotocol/protocolVersion": "2026-07-28",
                             "io.modelcontextprotocol/clientCapabilities": {}}}}
       """
@@ -612,10 +616,10 @@ Feature: Model Context Protocol
       content-type: application/json
       mcp-protocol-version: 2026-07-28
       mcp-method: tools/call
-      mcp-name: echo/GET
+      mcp-name: echo.GET
 
       {"jsonrpc": "2.0", "id": 11, "method": "tools/call",
-       "params": {"name": "echo/GET", "arguments": {"greeting": "hello"},
+       "params": {"name": "echo.GET", "arguments": {"greeting": "hello"},
                   "_meta": {"io.modelcontextprotocol/protocolVersion": "2026-07-28",
                             "io.modelcontextprotocol/clientCapabilities": {}}}}
       """

package/features/oauth.grants.feature

@@ -119,7 +119,7 @@ Feature: Authorization code flow
       id: 1
       result:
         tools:
-          - name: pots/GET
+          - name: pots.GET
       """
 
   Scenario: A code is spent once

package/features/rpc.feature

@@ -43,7 +43,7 @@ Feature: JSON-RPC
       accept: application/yaml
       content-type: application/json
 
-      {"jsonrpc": "2.0", "id": 1, "method": "pots/_id/GET",
+      {"jsonrpc": "2.0", "id": 1, "method": "pots._id.GET",
        "params": {"id": "4c4759e6f9c74da989d64511df42d6f4"}}
       """
     Then the following reply is sent:
@@ -67,7 +67,7 @@ Feature: JSON-RPC
       accept: application/yaml
       content-type: application/json
 
-      {"jsonrpc": "2.0", "id": 2, "method": "pots/POST",
+      {"jsonrpc": "2.0", "id": 2, "method": "pots.POST",
        "params": {"title": "Kettle", "volume": 1.7}}
       """
     Then the following reply is sent:
@@ -88,7 +88,7 @@ Feature: JSON-RPC
       accept: application/yaml
       content-type: application/json
 
-      {"jsonrpc": "2.0", "id": 3, "method": "pots/GET",
+      {"jsonrpc": "2.0", "id": 3, "method": "pots.GET",
        "params": {"query": {"limit": 1}}}
       """
     Then the following reply is sent:
@@ -108,7 +108,7 @@ Feature: JSON-RPC
       host: nex.toa.io
       content-type: application/json
 
-      {"jsonrpc": "2.0", "method": "pots/POST", "params": {"title": "Pot", "volume": 1}}
+      {"jsonrpc": "2.0", "method": "pots.POST", "params": {"title": "Pot", "volume": 1}}
       """
     Then the following reply is sent:
       """
@@ -123,7 +123,7 @@ Feature: JSON-RPC
       accept: application/yaml
       content-type: application/json
 
-      {"jsonrpc": "2.0", "id": 4, "method": "kettles/GET", "params": {}}
+      {"jsonrpc": "2.0", "id": 4, "method": "kettles.GET", "params": {}}
       """
     Then the following reply is sent:
       """
@@ -163,7 +163,7 @@ Feature: JSON-RPC
       accept: application/yaml
       content-type: application/json
 
-      {"jsonrpc": "2.0", "id": 17, "method": "pots/GET", "params": {}}
+      {"jsonrpc": "2.0", "id": 17, "method": "pots.GET", "params": {}}
       """
     Then the following reply is sent:
       """
@@ -216,7 +216,7 @@ Feature: JSON-RPC
       accept: application/yaml
       content-type: application/json
 
-      {"jsonrpc": "2.0", "id": 5, "method": "pots/_id/GET", "params": {}}
+      {"jsonrpc": "2.0", "id": 5, "method": "pots._id.GET", "params": {}}
       """
     Then the following reply is sent:
       """
@@ -236,7 +236,7 @@ Feature: JSON-RPC
       accept: application/yaml
       content-type: application/json
 
-      {"jsonrpc": "2.0", "id": 6, "method": "pots/faulty/GET", "params": {}}
+      {"jsonrpc": "2.0", "id": 6, "method": "pots.faulty.GET", "params": {}}
       """
     Then the following reply is sent:
       """
@@ -256,7 +256,7 @@ Feature: JSON-RPC
       accept: application/yaml
       content-type: application/json
 
-      {"jsonrpc": "2.0", "id": 7, "method": "pots/guarded/GET", "params": {}}
+      {"jsonrpc": "2.0", "id": 7, "method": "pots.guarded.GET", "params": {}}
       """
     Then the following reply is sent:
       """
@@ -271,10 +271,10 @@ Feature: JSON-RPC
       accept: application/yaml
       content-type: application/json
 
-      [{"jsonrpc": "2.0", "id": 8, "method": "pots/_id/GET",
+      [{"jsonrpc": "2.0", "id": 8, "method": "pots._id.GET",
         "params": {"id": "4c4759e6f9c74da989d64511df42d6f4"}},
-       {"jsonrpc": "2.0", "id": 9, "method": "kettles/GET", "params": {}},
-       {"jsonrpc": "2.0", "method": "pots/POST", "params": {"title": "Pot", "volume": 1}}]
+       {"jsonrpc": "2.0", "id": 9, "method": "kettles.GET", "params": {}},
+       {"jsonrpc": "2.0", "method": "pots.POST", "params": {"title": "Pot", "volume": 1}}]
       """
     Then the following reply is sent:
       """
@@ -299,9 +299,9 @@ Feature: JSON-RPC
       accept: application/yaml
       content-type: application/json
 
-      [{"jsonrpc": "2.0", "id": 13, "method": "pots/GET", "params": {}},
-       {"jsonrpc": "2.0", "id": 14, "method": "pots/GET", "params": {}},
-       {"jsonrpc": "2.0", "id": 15, "method": "pots/GET", "params": {}}]
+      [{"jsonrpc": "2.0", "id": 13, "method": "pots.GET", "params": {}},
+       {"jsonrpc": "2.0", "id": 14, "method": "pots.GET", "params": {}},
+       {"jsonrpc": "2.0", "id": 15, "method": "pots.GET", "params": {}}]
       """
     Then the following reply is sent:
       """
@@ -320,8 +320,8 @@ Feature: JSON-RPC
       host: nex.toa.io
       content-type: application/json
 
-      [{"jsonrpc": "2.0", "method": "pots/POST", "params": {"title": "One", "volume": 1}},
-       {"jsonrpc": "2.0", "method": "pots/POST", "params": {"title": "Two", "volume": 2}}]
+      [{"jsonrpc": "2.0", "method": "pots.POST", "params": {"title": "One", "volume": 1}},
+       {"jsonrpc": "2.0", "method": "pots.POST", "params": {"title": "Two", "volume": 2}}]
       """
     Then the following reply is sent:
       """
@@ -356,7 +356,7 @@ Feature: JSON-RPC
       accept: application/yaml
       content-type: application/json
 
-      {"jsonrpc": "1.0", "id": 10, "method": "pots/GET"}
+      {"jsonrpc": "1.0", "id": 10, "method": "pots.GET"}
       """
     Then the following reply is sent:
       """
@@ -394,8 +394,8 @@ Feature: JSON-RPC
       accept: application/yaml
       content-type: application/json
 
-      [{"jsonrpc": "2.0", "id": 11, "method": "pots/GET", "params": {}},
-       {"jsonrpc": "2.0", "id": 12, "method": "pots/GET", "params": {}}]
+      [{"jsonrpc": "2.0", "id": 11, "method": "pots.GET", "params": {}},
+       {"jsonrpc": "2.0", "id": 12, "method": "pots.GET", "params": {}}]
       """
     Then the following reply is sent:
       """
@@ -421,7 +421,7 @@ Feature: JSON-RPC
       accept: application/yaml
       content-type: application/json
 
-      {"jsonrpc": "2.0", "id": 9, "method": "pots/GET", "params": {}}
+      {"jsonrpc": "2.0", "id": 9, "method": "pots.GET", "params": {}}
       """
     Then the following reply is sent:
       """

package/features/steps/Gateway.ts

@@ -158,8 +158,9 @@ export class Gateway {
     /*
      * The gateway waits for the branches it discovers, but a component's own resources —
      * a storage, a queue — are still connecting when it answers. Fifty milliseconds was
-     * enough until the composition grew; a scenario that asks too early reads the 404 that
-     * precedes the route.
+     * enough until the composition grew, then a hundred; a scenario that asks too early
+     * reads the 404 that precedes the route, which `realtime` was failing on in two runs
+     * of three. It is a sleep and not a poll, so it is raised rather than fixed.
      */
     await timeout(DISCOVERY)
   }
@@ -217,7 +218,7 @@ const DEFAULT_TREE = JSON.stringify({
 } satisfies syntax.Node)
 
 /** Milliseconds a composition is given to finish connecting what it needs. */
-const DISCOVERY = 100
+const DISCOVERY = 500
 
 const DEFAULT_PROPERTIES: Partial<http.Options> = {
   authorities: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@toa.io/extensions.exposition",
-  "version": "1.0.0-alpha.284",
+  "version": "1.0.0-alpha.285",
   "type": "module",
   "description": "Toa Exposition",
   "author": "temich <tema.gurtovoy@gmail.com>",
@@ -58,5 +58,5 @@
     "@types/cors": "2.8.19",
     "@types/negotiator": "0.6.5"
   },
-  "gitHead": "006755556879e91e8d68fa86753aa3b475bdf4bf"
+  "gitHead": "44ed1be7e322a5ea8f1a8ed85ba96b9dfaf28224"
 }

package/source/Introspection.ts

@@ -8,6 +8,9 @@ export interface Introspection {
    * one sentence cannot be true of both. The operation's own is for the Introspection.
    */
   description?: string
+
+  /** what a person is shown where a client lists this method, which a name is not */
+  title?: string
   route?: Record<string, Schema>
   query?: Record<string, Schema>
 
@@ -40,7 +43,7 @@ export function order (introspection: Introspection): Introspection {
   return ordered
 }
 
-const KEYS = ['description', 'route', 'query', 'headers', 'input', 'output', 'errors'] as const
+const KEYS = ['title', 'description', 'route', 'query', 'headers', 'input', 'output', 'errors'] as const
 
 /**
  * The schema of one input property, taken out of it: a property another family fills is

package/source/MCP/tools.ts

@@ -54,6 +54,7 @@ export async function list (tree: Tree, context: http.Context): Promise<Tool[]>
     // in the order the revision documents one, which is the order it is read in
     const tool: Tool = {
       name: named,
+      ...introspection.title === undefined ? {} : { title: introspection.title },
       ...described === undefined ? {} : { description: described },
       inputSchema: input(introspection, variables.map((variable) => variable.name)),
       ...schema === undefined ? {} : { outputSchema: schema },

package/source/MCP/types.ts

@@ -66,7 +66,10 @@ export interface Content {
 export interface Tool {
   name: string
 
-  /** what the operation states it is; absent where it states nothing */
+  /** what a person is shown where a client lists this tool; a name is an address */
+  title?: string
+
+  /** what the route states this method is */
   description?: string
   inputSchema: object
   outputSchema?: object