Skip to main content
Glama

Cnamio

Cnamio integration guide

get_integration_guide
Read-only

Returns the step-by-step guide to add custom domain connection to a project with Cnamio: records, environment variables, server session route, browser connect window, headless API and webhook verification (Node.js and Python). Start here when integrating Cnamio into code.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_integration_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that the returned artifact is procedural documentation spanning records, env vars, server session routes, browser connect window, headless API and webhook verification, and that samples are in Node.js and Python — useful context about what comes back with no output schema to declare it.

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?

One sentence, front-loaded with the core verb and resource, with the topic list serving a real disambiguation purpose. The mid-sentence enumeration is dense but every item maps to content an integrator would need, so little could be cut without loss.

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 zero-parameter read tool with no output schema, the description adequately tells the agent what the response contains and when to fetch it. It could go slightly further by indicating format or size of the returned guide, but nothing essential is missing for correct invocation.

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?

There are zero parameters, so the baseline is 4. The description correctly implies no configuration is needed, but adds nothing further on parameters because there are none to disambiguate.

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 ("Returns the step-by-step guide to add custom domain connection to a project with Cnamio") and then enumerates the exact topics the guide covers, so an agent can distinguish this reference tool from the action siblings like connect_domain or check_domain.

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?

"Start here when integrating Cnamio into code" gives a clear entry-point condition for choosing this tool over the siblings. It stops short of explicit when-not guidance or naming any sibling directly, which keeps it out of 5 territory.

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