Read the cached individual tool definitions for an owned connection. These functions are exposed separately to the voice agent on calls after set_agent_connectors assigns the connection. This read does not invoke them, refresh discovery or return credentials.
| Name | Required | Description | Default |
|---|---|---|---|
| connector_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Output schema / anyOfPrevious value: -[
- {
- "additionalProperties": {},
- "properties": {
- "operation_id": {
- "type": "string"
- },
- "status": {
- "type": "string"
- },
- "tools": {
- "items": {
- "additionalProperties": {},
- "propertyNames": {
- "type": "string"
- },
- "type": "object"
- },
- "type": "array"
- }
- },
- "required": [
- "tools",
- "status"
- ],
- "type": "object"
- },
- {
- "additionalProperties": {},
- "properties": {
- "error": {
- "type": "string"
- },
- "message": {
- "type": "string"
- }
- },
- "required": [
- "error"
- ],
- "type": "object"
- },
- {
- "additionalProperties": {},
- "properties": {
- "message": {
- "type": "string"
- },
- "next_action": {
- "type": "string"
- },
- "operation_id": {
- "type": "string"
- },
- "status": {
- "type": "string"
- }
- },
- "required": [
- "operation_id",
- "status"
- ],
- "type": "object"
- }
-]New value: +[
+ {
+ "additionalProperties": {},
+ "properties": {
+ "connector_id": {
+ "maxLength": 200,
+ "minLength": 1,
+ "type": "string"
+ },
+ "execution_context": {
+ "const": "voice_agent",
+ "type": "string"
+ },
+ "operation_id": {
+ "type": "string"
+ },
+ "status": {
+ "type": "string"
+ },
+ "tools": {
+ "items": {
+ "additionalProperties": {},
+ "properties": {
+ "annotations": {
+ "additionalProperties": {},
+ "properties": {
+ "destructiveHint": {
+ "type": "boolean"
+ },
+ "idempotentHint": {
+ "type": "boolean"
+ },
+ "openWorldHint": {
+ "type": "boolean"
+ },
+ "readOnlyHint": {
+ "type": "boolean"
+ },
+ "title": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "description": {
+ "type": "string"
+ },
+ "inputSchema": {
+ "additionalProperties": {},
+ "properties": {
+ "type": {
+ "const": "object",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type"
+ ],
+ "type": "object"
+ },
+ "name": {
+ "type": "string"
+ },
+ "outputSchema": {
+ "additionalProperties": {},
+ "properties": {
+ "type": {
+ "const": "object",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type"
+ ],
+ "type": "object"
+ },
+ "title": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "name",
+ "inputSchema"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "connector_id",
+ "execution_context",
+ "status",
+ "tools"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": {},
+ "properties": {
+ "error": {
+ "type": "string"
+ },
+ "message": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "error"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": {},
+ "properties": {
+ "message": {
+ "type": "string"
+ },
+ "next_action": {
+ "type": "string"
+ },
+ "operation_id": {
+ "type": "string"
+ },
+ "status": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "operation_id",
+ "status"
+ ],
+ "type": "object"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Goes well beyond the readOnly/idempotent annotations by disclosing that the data is cached, that the call does not invoke the tools, does not refresh discovery, and does not return credentials. These are exactly the side-effect boundaries an agent needs to know before relying on results.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with the core action, then lifecycle context, then exclusions. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, the description need not describe return values, and it correctly focuses on caching semantics and non-behaviors. It is nearly complete; only the explicit when-to-call-this-tool guidance is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% for the single connector_id parameter, and the description only implies via 'owned connection' that the ID must belong to the caller. It adds a useful ownership constraint but not enough detail (format, lookup source, error behavior) to fully compensate for the undocumented schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: 'Read the cached individual tool definitions for an owned connection.' The word 'cached' plus 'individual tool definitions' distinguishes it from list_connectors and from set_agent_connectors without requiring the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explains the lifecycle context (these tools become exposed to the voice agent after set_agent_connectors assigns the connection) and clarifies what the read does not do. However, it never states directly when an agent should call this versus alternatives like list_connectors or execute-style tools, so usage must be inferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.