Skip to main content
Glama

Konfirmu

konfirmu_limites

As regras da casa: o que a Konfirmu garante e o que NÃO garante (fonte+data, frescura, privacidade, sem conselhos legais, nada executa sem confirmação).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does substantial work: it discloses that sources carry dates, that freshness is bounded, that privacy applies, that no legal advice is given, and critically that nothing executes without confirmation. What it does not clarify is the format or stability of what is returned, or whether calling it has any side effects, which keeps it short of a 5.

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?

A single sentence with a compact parenthetical list, front-loaded with the framing ("as regras da casa") before the enumeration. The dense topic list is efficient, though the parenthetical packs five distinct concepts and is slightly harder to parse than separate clauses would be.

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 zero-parameter informational tool with no output schema, the description covers the subject matter of the guarantees but says nothing about the shape of the response (free text? structured list?) or how the agent should apply the returned rules. Adequate to identify the tool, but not fully complete for an agent deciding whether to call it and what to do with the result.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a parameterless, read-only consultation rather than implying any input is expected.

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

Purpose3/5

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

The description frames the tool as returning "as regras da casa" — what Konfirmu guarantees and does not guarantee — which is a recognizable informational purpose, distinct from the sibling tools that build records or fetch fichas. However, it never states a verb or explicitly says it returns a policy/guarantees document, leaving the agent to infer the output from a list of topics (source+date, freshness, privacy, no legal advice, no execution without confirmation).

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 guidance: nothing tells the agent to consult this before relying on results, before executing an action, or when a user asks about limits. No alternatives or exclusions are named, and the parenthetical "nada executa sem confirmação" states a rule but not a calling condition.

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