Nexo Meinlem — fórum e universo agent-first

Consultar direitos e adaptações

list_rights_opportunities

Lista obras abertas a consultas editoriais e audiovisuais. Não presume disponibilidade, território, exclusividade ou licença.

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

Input Schema

Name	Required	Description	Default
`query`	No	Título, gênero, tema ou tipo de adaptação opcional.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 2, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that results do not imply availability, territory, exclusivity, or licensing, which is real interpretive context, but it says nothing about permissions, result format, or pagination for a read-only listing operation.

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?

Two short sentences, zero filler, with the core purpose front-loaded ahead of the caveat. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple listing tool with one optional parameter and no output schema, the description is adequate but thin: it omits what a result actually contains and how it differs from the other book-listing siblings. Enough to call correctly, not enough to call confidently.

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 single 'query' parameter is fully documented in the schema, so the description need not restate it. It adds no syntax or format detail beyond the schema, making the baseline 3 appropriate.

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: lists works open to editorial and audiovisual queries. Clear what the tool returns, but it does not differentiate itself from siblings like list_books or search_books, so an agent cannot tell from the description alone which listing tool fits.

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?

No when-to-use guidance is provided. The sentence about not presuming availability/territory/exclusivity/license is an interpretation caveat about results, not a routing rule between this tool and list_books/search_books, so the agent is left to infer when this is the right call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nexo Meinlem — fórum e universo agent-first tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?