Skip to main content
Glama

Startups Españolas press desk

Status of a submission

estado_nota
Read-onlyIdempotent

Status of a submission by ticket: waiting for confirmation, in review, published (with URL), rejected, answered by email, waiting for payment, expired. Read only.

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": {
      "ticket": "<ticket>"
    },
    "name": "estado_nota"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticketYesTicket returned by enviar_nota.
languageNoAnswer language, default es.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so "Read only" adds nothing. The real value is the disclosure of the possible outcomes — including that 'published' returns a URL and 'answered by email' exists — which tells the agent what results to expect from a tool with no output schema.

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

Conciseness5/5

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

A single front-loaded sentence that packs the resource, key, and full status enumeration with zero filler; the trailing safety note is the only mildly redundant element.

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 lookup with no output schema, the description covers what an agent needs: how to identify the submission and what the returned states mean. It stops short of stating what a not-found or invalid ticket response looks like.

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 description coverage is 100%, so both parameters (ticket, language with enum es/en) are already documented in structured data. The description only restates 'by ticket' and adds no format, validation, or default semantics beyond the schema.

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 specific resource and access key: the status of a submission, retrieved by ticket, and enumerates the status space. It is clearly distinct from enviar_nota (submit), ver_condiciones, and ver_medios without needing to name them.

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?

Usage is implied by the mention that the ticket is the identifier, and the schema says the ticket comes from enviar_nota, so an agent can infer this is the follow-up call after submitting. There is no explicit when-to-use/when-not guidance or named alternative, leaving routing to inference.

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.