Meta Council

Update Consulting Client

update_consulting_client

Destructive

Update mutable fields on an owned consulting client.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "client_id": "<client_id>"
    },
    "name": "update_consulting_client"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`notes`	No
`status`	No
`client_id`	Yes
`contact_name`	No
`organization`	No
`contact_email`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "text": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "text"
-  ],
-  "type": "object"
-}New value: +null

AddedJul 22, 2026

TDQS

C2.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare non-read-only, non-idempotent, and destructiveHint=true. The description's phrase 'mutable fields' adds a small hint that partial updates are supported and some fields are immutable, but it never explains what makes this destructive, whether unspecified fields are preserved or cleared, or whether ownership enforcement applies. Given annotations carry the safety profile, a 3 is fair.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence is front-loaded and waste-free, but here the brevity reflects under-specification rather than tightness. Given a 7-parameter mutation with no schema descriptions, more detail was warranted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, non-idempotent mutation with 7 undocumented parameters and no output schema, the description is far too thin. It omits which fields are updatable, merge semantics, ownership/permission requirements, and failure behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 7 parameters, so the schema contributes nothing beyond names and types. The description says only 'mutable fields' and enumerates none of them; it doesn't clarify whether omitting a field leaves it unchanged, which is critical for a partial-update tool. It fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Update) and resource (consulting client), and adds scope qualifiers: 'mutable fields' and 'owned'. This distinguishes it from create_consulting_client and get/list counterparts, though it doesn't name any sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, no alternatives named. The agent must infer that this is the tool for editing an existing client rather than creating one.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Meta Council tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?