Skip to main content
Glama

Ler templates de mensagem do bot

get_template
Read-only

Lê os templates do bot — tanto o FORMATO das ofertas (oferta, cupom, rodapé e rodapé por marketplace) quanto as mensagens de RESPOSTA (boas-vindas, uso de comando, carregando, sucesso, erro, entrega de link, modo inline). Para descobrir QUAIS chaves existem, use keys_only:true (resposta barata: chave, modo e editable — true quando set_template aceita a chave); para ler o texto de um template, informe "key" (ex.: format.post.footer.shopee, command.start.welcome); omitir ambos retorna todos os textos completos (resposta grande, ~70 templates).

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

Input Schema

NameRequiredDescriptionDefault
keyNoOpcional. Chave do template (ex.: format.post.footer.shopee, command.start.welcome).
keys_onlyNoSe true, lista só as chaves (sem o texto) — use para descobrir o que existe antes de ler/editar.

Output Schema

NameRequiredDescriptionDefault
itemsNoTemplates: key, mode, editable (e text quando pedido).
successNo
editable_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, but the description adds real behavioral context: the keys_only response is cheap (chave, modo, editable), omitting both returns ~70 full templates as a large response, and editable=true signals that set_template accepts the key. That is exactly the extra context an agent needs to avoid an accidental expensive 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?

Information is front-loaded: what it reads, then how to call it in each of the three modes. It is dense and mostly one long paragraph, with a few run-on clauses, but almost every clause earns its place (response size, editable semantics, examples).

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

Completeness5/5

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

For a read-only two-parameter tool with an output schema, nothing an agent needs is missing: what is returned in each mode, relative response cost, and how it relates to the editing sibling. Return value shapes can be left to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented, but the description adds value beyond it: it explains the default-omission semantics (both omitted returns all texts) and gives concrete key examples. It stops short of exhaustively describing key namespaces, hence a 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (lê) and resource (templates do bot) and enumerates the two families covered: offer FORMATO templates and RESPOSTA messages. It is immediately distinguishable from set_template, which is named for the editable flag, and from the rest of the siblings.

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

Usage Guidelines5/5

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

Gives explicit mode selection: keys_only:true to discover which keys exist (the cheap response), key to read one template's text, neither to read all. It also names the editing counterpart (set_template) and the editable flag's purpose, leaving no ambiguity about when to use each mode.

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.

Resources