Skip to main content
Glama

Get ClawCall calling guide

get_calling_guide
Read-only

Use this when building a ClawCall call request or explaining how ClawCall works. Returns a markdown guide maintained with the ClawCall server: outbound (request fields and call workflow), examples (complete requests), errors, profile, inbound, privacy, or webhooks. call_format structured returns guides for the current call fields.

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": {
      "topic": "<topic>",
      "call_format": "<call_format>"
    },
    "name": "get_calling_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesThe guide topic for the work: outbound, examples, errors, profile, inbound, privacy, or webhooks.
call_formatYesUse structured to read guides matching the current call fields.

Output Schema

NameRequiredDescriptionDefault
markdownYesThe complete calling guide in Markdown, also returned as text content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered; the description adds that the content is a markdown guide maintained server-side, meaning it reflects current server behavior rather than being static. It also explains that call_format=structured tailors the guide to the current call fields, which is behavioral context not present in the annotations.

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

Conciseness4/5

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

The usage trigger is front-loaded in the first sentence, followed by return content and then the call_format note, so the structure matches how an agent decides. It is dense but not padded; the final sentence is slightly compressed and reads awkwardly ('call_format structured returns guides...'), costing a point.

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

Completeness4/5

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

For a two-parameter, read-only documentation tool with an output schema and full schema coverage, the description covers what it returns, which topics exist, and the purpose of the const parameter. Nothing essential for correct invocation is missing, though a hint about guide size or whether topics can be combined would have made it fully complete.

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

Parameters4/5

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

Schema coverage is 100%, so baseline would be 3, but the description earns more by glossing what each topic contains, e.g. 'outbound (request fields and call workflow)' and 'examples (complete requests)', which helps the agent pick the right enum value. The call_format sentence clarifies that 'structured' aligns the guide with the current call fields, adding intent beyond the bare const.

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?

The description states a clear verb and resource: it 'Returns a markdown guide' maintained with the ClawCall server, and it enumerates the topic set (outbound, examples, errors, profile, inbound, privacy, webhooks). This is distinguishable from action-oriented siblings like place_call or get_call because it is documentation retrieval rather than call manipulation, though it never explicitly contrasts itself with them.

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

Usage Guidelines4/5

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

'Use this when building a ClawCall call request or explaining how ClawCall works' gives a concrete triggering condition, which tells the agent to reach for this before composing a request. It stops short of explicit when-not guidance or naming an alternative tool for overlapping questions, so it is clear context without exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.