Skip to main content
Glama

Sirfus CAR

Get status updates pushed to a URL

car_set_webhook

Registers an https URL that receives a POST on every change of this agent's requests (status and loop stage), signed with the returned secret: CAR-Signature: t=,v1=<hex HMAC-SHA256(secret, ".")>. The secret is shown once. Up to 5 per agent.

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": {
      "url": "<url>"
    },
    "name": "car_set_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttps URL (port 443, a host name) that receives a signed POST on every change of your requests

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations, which only declare mutation, non-idempotency, and open-world reach: it specifies the exact delivery mechanism (signed POST), the signature header and HMAC construction, the show-once secret handling, and a per-agent registration limit. These are the details an agent needs to use and reason about the side effect.

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?

Only three compact sentences, with the core action front-loaded before the signature spec. The HMAC template is dense but each element (header name, timestamp, digest input) earns its place; a light structural break for the header format would help readability.

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?

With one required parameter, an output-less contract, and annotations covering the safety profile, the description closes the remaining gaps itself: the secret is the only return value and it is explicitly shown once, and the registration cap is stated. Nothing needed to call it correctly is missing.

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% and already documents url as an https host on port 443, so the baseline would be 3; the description reinforces what that URL will receive and ties it to the signature contract. It adds meaning but no new syntactic constraints beyond the schema.

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 ('Registers an https URL that receives a POST on every change of this agent's requests') and names the exact events it fires on (status and loop stage). No sibling tool is a registration endpoint, so an agent can identify this unambiguously.

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?

Conveys the trigger context implicitly (this is the push alternative to polling car_check_status), but never states when to prefer it, whether it replaces polling, or how to remove/replace an existing webhook. The 'Up to 5 per agent' cap is the only operational constraint given.

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.

Resources