Skip to main content
Glama

licenca_formal

Consulta a oferta de licenca sobre fotografia da coleccao FISICA 0001sensations. Devolve a resposta HTTP e o desafio x402 do servidor, incluindo selecao e URL canonico quando presentes. Esta ferramenta nao envia comprovativo, nao paga nem emite licenca. A entrega da fotografia depende do percurso pago anunciado pelo servidor. Nao transfere obra fisica, exclusividade ou NFT. Catalogo gratuito em ora-licenca/catalogo. (a partir de 1.618 USDC)

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

Input Schema

NameRequiredDescriptionDefault
obraNoid (1-108) ou titulo de uma obra fisica. Sem isto, escolhe-se uma obra ao acaso entre as preservadas.
tipoNoconsulta | editorial | treino. Ver ora-licenca/catalogo para precos e direitos. Incide sobre a coleccão fisica (107 obras).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / obra / maxLength
      Added value: +200
    • addedInput schema / properties / tipo / enum
      Added value: +[
      +  "consulta",
      +  "editorial",
      +  "treino"
      +]
    • addedInput schema / required
      Added value: +[]
  2. Changed2 schema fields changed
    • changedInput schema / properties / obra / description
      Previous value: -"Titulo ou token_id da obra (nao aplicavel a arquivo)."New value: +"id (1-108) ou titulo de uma obra fisica. Sem isto, escolhe-se uma obra ao acaso entre as preservadas."
    • changedInput schema / properties / tipo / description
      Previous value: -"preview | editorial | treino | arquivo. Ver ora-licenca/catalogo para precos e direitos."New value: +"consulta | editorial | treino. Ver ora-licenca/catalogo para precos e direitos. Incide sobre a coleccão fisica (107 obras)."
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

The description adds substantial behaviour beyond the annotations: it explicitly says it does not send a proof, does not pay and does not issue a licence, that delivery depends on the server's paid path, and that no physical work, exclusivity or NFT is transferred, plus a price floor of 1.618 USDC. One gap remains: with readOnlyHint=false and idempotentHint=false, the description never explains what server-side state changes (presumably the x402 challenge/session creation), so the agent cannot tell why this is a non-read-only call.

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?

Front-loaded with what the tool does, then the return shape, then the negative scope, then the catalogue pointer and price. Most sentences carry weight, though the three separate disclaimers (no proof/no payment/no licence, no physical work/exclusivity/NFT) could be merged without loss.

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-optional-parameter tool with no output schema, the description covers the action, the response contents, the negative guarantees and the pricing pointer, which is close to enough to call it correctly. It falls short only on why the operation is flagged non-read-only and non-idempotent, and on how it relates to the sibling licence tools.

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 both the 'obra' id/title-or-random behaviour and the 'tipo' enum meanings, so the baseline applies. The description adds nothing about the parameters themselves ('selecao e URL canonico' refers to the response, not inputs), so it neither compensates nor detracts.

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: 'Consulta a oferta de licenca sobre fotografia da coleccao FISICA 0001sensations', and clarifies the return (HTTP response plus x402 challenge with selection and canonical URL). The purpose is unambiguous, but it never distinguishes itself from the sibling licence/NFT tools (nft_catalogo, nft_dedicar), leaving the agent to infer which one to call.

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 rather than stated: it says delivery depends on 'o percurso pago anunciado pelo servidor' and points to 'ora-licenca/catalogo' for free browsing and pricing, which hints at a pre-purchase step. There is no explicit 'use this before X' or 'use sibling Y instead' routing, and no prerequisites are spelled out.

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.