Skip to main content
Glama

Startups Españolas press desk

Submit a press release

enviar_nota

Submits a press release for review. We email a confirmation request to the given sender address; the review starts only after that email is answered. Publication is an editorial decision, not guaranteed. Free allowance and packages apply per sender address (see ver_condiciones). Moves no money.

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": {
      "email": "<email>",
      "empresa": "<empresa>",
      "titulo": "<titulo>",
      "texto": "<texto>"
    },
    "name": "enviar_nota"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesEmail address of the agency or company that sends the release. It receives the confirmation request, offers and invoices.
textoYesFull text of the release, 400 to 20,000 characters, plain text or simple paragraphs.
nombreNoContact person (optional).
tituloYesHeadline (max 200 characters).
embargoNoEmbargo date, ISO format (optional).
empresaYesCompany the release is about (max 120 characters).
languageNoAnswer language, default es.
web_empresaNoCompany website (optional).
medio_preferidoNoPreferred publication; only a hint, the editorial review decides.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the double opt-in flow: a confirmation request is emailed to the sender and the review only begins once it is answered. It also states that publication is not guaranteed, that allowance is scoped per sender address, and that the tool moves no money — behavior an agent could not derive from readOnlyHint/openWorldHint/destructiveHint alone.

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?

Four short sentences, front-loaded with the action first, then the gating workflow, then the outcome caveat, then quota and the money clarification. Nothing redundant and nothing buried.

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 9-parameter write tool with no output schema, the description covers the essential behavioral contract: confirmation gating, non-guaranteed outcome, quota scoping, and no financial side effects. The main gap is that it never says what a successful call returns or how to follow up on a pending submission.

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%, so every parameter is already documented in the input schema. The description adds only the per-sender-address allowance scoping, which highlights the significance of the email parameter, but adds no format or constraint detail 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?

States a specific verb and resource ('Submits a press release for review') and makes the scope clear: submission for editorial review, not publication. It routes quota questions to ver_condiciones but doesn't differentiate itself from estado_nota or ver_medios, so an agent still has to infer the lifecycle split.

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?

The when-to-use case (send a release for review) is implied clearly, and the ver_condiciones pointer gives one useful alternative for pricing/quota questions. However, there is no explicit guidance on checking submission status afterwards (estado_nota) or on what to do if the confirmation email is never answered.

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.