Skip to main content
Glama

Compara MEI: card machines, websites, e-commerce, CRM and ERP for Brazilian small businesses

Kit para um tipo de negócio

kit_para_negocio
Read-onlyIdempotent

Monta um kit inicial (maquininha, site ou loja virtual, gestão/nota fiscal, CRM) para um tipo de negócio, ex.: 'delivery de marmita', 'salão de beleza', 'loja de roupas online', 'eletricista'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "negocio": "<negocio>"
    },
    "name": "kit_para_negocio"
  }
}

Input Schema

NameRequiredDescriptionDefault
negocioYes
orcamento_baixoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds what the bundle conceptually contains, but says nothing about how the kit is produced (curated vs. generated), whether items carry prices, or how the low-budget flag changes the result.

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?

One front-loaded sentence with the artifact first and the parameter examples second; nothing is redundant. The parenthetical component list and example set both earn their space by defining scope and input format.

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 read-only curation tool with no output schema, the description covers what goes in but not what comes back (product entries? links? prices?), which matters when sibling tools return product-level data. It is adequate to invoke, but an agent cannot predict the response shape or how to combine the kit with product lookups.

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 0%, so the description must carry the parameter burden. It does well for 'negocio', giving four illustrative values that clarify the expected granularity, but 'orcamento_baixo' is never mentioned, leaving an agent to guess that it constrains the kit to cheaper options.

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 states a concrete verb and artifact: it assembles a starter kit (card machine, site/virtual store, invoicing/management, CRM) for a business type. The enumerated kit components and the four example business types make the scope unambiguous, though it never contrasts itself with sibling tools like buscar_produtos or alternativas.

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 by 'para um tipo de negócio' plus examples such as 'delivery de marmita' and 'eletricista', which shows the expected input context. There is no explicit when-to-use/when-not-to-use guidance and no pointer to the sibling tools an agent should pick instead when it wants a single product or a comparison.

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