Skip to main content
Glama

Look up a website draft

ver_borrador
Read-onlyIdempotent

Use this when someone has a draft link or token from crear_borrador_web and wants to know its state: business name, list of pages, whether it is still valid and until when. Read only; changes nothing.

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": {
      "draft": "<draft>"
    },
    "name": "ver_borrador"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftYesThe draft link (https://palimpalem.com/palim/apli/entwurf.php?t=...) or just its 24-character token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Read only; changes nothing' is largely a restatement. The genuinely additive part is the disclosure of returned state fields (business name, pages, validity, expiry), which matters because there is no output schema. It does not say how an invalid or expired token is surfaced (error vs. flag).

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?

Two sentences, front-loaded with the selection trigger followed by the return contents. The trailing 'Read only; changes nothing' clause is mildly redundant against the annotations but is short enough not to bloat the definition.

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 one-parameter read tool with no output schema, the description covers the selection trigger and the shape of the result, which is the important gap it needed to fill. The remaining omission is failure behavior for an expired or unknown token, which an agent would want to know before presenting results.

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

Parameters3/5

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

Schema coverage is 100% and the schema already documents the single 'draft' parameter including both accepted forms (full URL with the t= query or the 24-character token). The description repeats 'draft link or token' without adding syntax, normalization, or error-handling detail beyond the schema, so the baseline 3 applies.

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 (look up) and resource (website draft) plus the exact payload returned: business name, page list, validity and expiry. It also anchors the tool to the sibling crear_borrador_web as the source of the token, so an agent can distinguish it from creation/claim tools 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 Guidelines4/5

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

The trigger condition is explicit: 'use this when someone has a draft link or token from crear_borrador_web and wants to know its state.' That gives a clear when-to-use. It stops short of naming when-not-to-use or pointing at other siblings such as reclamar_borrador for the claim path or editar_web for modifications.

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.