Skip to main content
Glama

Startups Españolas press desk

List the publications

ver_medios
Read-onlyIdempotent

Lists the active publications of the network with name, URL, topics covered, what each accepts and the link to its criteria page. Read only.

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": "ver_medios"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoAnswer language, default es.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, and the closing "Read only." merely restates them. The genuinely additive part is the disclosure of what the response contains (name, URL, topics, accepted formats, criteria link), which matters because no output schema exists. It does not mention ordering, pagination, or what makes a publication "active" versus inactive.

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?

The main sentence is dense but front-loaded with the verb and resource, followed by the returned fields. The trailing "Read only." is redundant with the annotations and is the only wasted text.

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?

With no output schema, the enumeration of returned fields is essential and is supplied here, and the single optional parameter is fully documented in the schema. Remaining gaps — whether "active" implies filtering, response ordering, and the link to ver_condiciones — are minor for a simple listing tool.

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?

There is a single optional parameter with 100% schema description coverage and an enum, so the schema already explains that `language` selects the answer language and defaults to "es". The description adds no extra meaning about the parameter, which is acceptable given full schema coverage — baseline 3 applies.

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 uses a specific verb ("Lists") tied to a specific resource ("active publications of the network") and enumerates the fields returned, so an agent knows exactly what the tool surfaces. It does not explicitly distinguish itself from the siblings (ver_condiciones, enviar_nota, estado_nota), but the scope is concrete enough to infer the difference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The mention of the "link to its criteria page" hints that this is a discovery step before ver_condiciones, but the description never states that relationship or any prerequisite.

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.