Sergio by Serviche

Say where leads come from

declare_lead_sources

Idempotent

Records where the business gets its leads (keys from the setup guide list, for example thumbtack, google_lsa, yelp, website, other; other needs its words), as Get started's lead sources step does. An answer only: it opens and sends nothing. Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.

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": {
      "keys": "<keys>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "declare_lead_sources"
  }
}

Input Schema

Name	Required	Description
`keys`	Yes
`other`	No
`reason`	No	Why you are doing this, in one sentence. The owner sees it in the notice Sergio sends after the change.
`idempotency_key`	Yes	Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the annotations, the description discloses that it 'opens and sends nothing' (no outbound messaging) and that it is an owner-level change where 'Sergio tells the owner after it is made' — a real side effect not captured by the hints. It also reinforces the idempotency contract. It stops short of describing the response or failure behavior, but the added context is meaningful.

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?

Dense but front-loaded: the core action and its scope come first, followed by the no-send clarification, retry rule, and notification note. Phrasing is slightly compressed ('other needs its words') but every sentence carries information.

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 4-parameter mutation with no output schema, the description covers the key semantics, the idempotency contract, the absence of outbound sends, and the owner notification side effect. What remains (return shape, validation failures) is minor for this tool.

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?

With 50% schema coverage, the description compensates by explaining that keys come from the setup guide list, giving examples, and clarifying that 'other needs its words' — linking the keys and other parameters. The reason and idempotency_key parameters are left to the schema, which documents them adequately.

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 ('Records where the business gets its leads') and anchors it to a concrete setup step, with example keys (thumbtack, google_lsa, yelp, website, other). An agent can distinguish this from siblings like edit_lead_step or set_lead_outcome without opening the schema.

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

Usage Guidelines3/5

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

It gives retry guidance ('Pass the same idempotency_key when retrying') and frames the tool as the Get started lead-sources step, which implies when to use it. However, it never names an alternative or states when NOT to use it versus related tools such as edit_lead_step, leaving the routing inference to the agent.

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

All Sergio by Serviche 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?