Ranksmile

Update workspace context

workspace__update_context

Destructive

Save what you learned so the editor and other agents use it. Ops apply in order; if one is invalid, none is applied. To ADD a fact to the brand notes use {"append_brand_knowledge": "..."}: it keeps everything already there. {"brand_knowledge": "..."} REPLACES the whole notes ("" clears them): use it only to rewrite or shorten, after reading them with workspace__get_context. The notes hold at most 4000 characters. {"append_research_log": ": . Verdict: "} records research you did (max 500 chars). Confirm facts with the user before storing them. Returns the updated context.

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": {
      "workspace_id": "<workspace_id>",
      "updates": "<updates>"
    },
    "name": "workspace__update_context"
  }
}

Input Schema

Name	Required	Description	Default
`updates`	Yes
`workspace_id`	Yes	From workspace__list.

Output Schema

Name	Required	Description
`domain`	Yes
`voices`	No
`missing`	Yes
`brand_name`	No
`competitors`	No	Domains competing in search: domain, appearances, avg_position.
`research_log`	Yes	The newest 20 entries of the last 90 days, newest first: id, summary, author, created_at, age_days.
`workspace_id`	Yes
`brand_knowledge`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A5/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses atomicity ('if one is invalid, none is applied'), ordered op application, character budgets (4000/500) and the destructive 'replaces the whole notes / "" clears them' semantics. This coherently explains why destructiveHint=true and idempotentHint=false are set.

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

Conciseness5/5

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

Purpose is front-loaded in the first sentence, then each following sentence covers exactly one operational fact (atomicity, append vs replace, limits, log format, user confirmation). Dense but zero redundancy.

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

Completeness5/5

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

Output schema exists and the description confirms 'Returns the updated context', so return values need no elaboration. For a mutation tool with nested ops, atomic behavior, and limits, the description covers everything an agent needs to invoke it safely.

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

Parameters5/5

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

Schema coverage is only 50% (only workspace_id is described), so the description must carry the nested updates keys – and it does, defining each operation's intent, a concrete log format template, and limits. It adds substantial meaning beyond the bare property names.

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

Purpose5/5

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

States a specific verb and resource ('Save what you learned' into workspace context) and makes the intended consumers explicit ('the editor and other agents'). It is clearly distinguishable from the sibling workspace__get_context, which it even references as the read counterpart.

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

Usage Guidelines5/5

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

Explicitly routes between operations: use append_brand_knowledge to ADD, brand_knowledge only to rewrite/shorten after reading via workspace__get_context. Adds the process guidance 'Confirm facts with the user before storing them' – a real when-to-use constraint rather than inference.

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

All Ranksmile 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?