Skip to main content
Glama

massa

by dev.criando
OverviewDiscussionsAdmin

Gerar massa de teste

gerar
Read-only

Gera massa de teste a partir de um schema JSON do massa e devolve o arquivo como texto (csv, json ou script sql). Até 100 linhas por chamada; acima disso nada é gerado e a resposta traz o schema e um curl para a API (/api/generate), que gera o volume todo. Com formato xlsx (Excel), devolve um link que baixa o arquivo, sem o teto de linhas: mostre o link ao usuário exatamente como veio. Sem seed no schema, uma é sorteada e devolvida: com a mesma seed e o mesmo schema, o resultado é idêntico. Schema inválido volta como erro com as mensagens campo a campo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
schemaYeso schema JSON do massa, como objeto
tabelaNonome da tabela dos INSERT, só com formato sql (aceita esquema.tabela; padrão massa)
dialetoNobanco do script, só com formato sql: mysql, oracle ou sqlserver. Vazio é SQL padrão (Postgres)
formatoNocsv (padrão), json, sql ou xlsx (Excel: volta um link para baixar o arquivo, que não entra no contexto)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
curlNocomando que gera o volume todo pela API, só acima do teto
linkNosó xlsx: endereço que baixa o arquivo Excel; mostre-o ao usuário sem alterar nada
seedYesseed usada; repita-a para obter o mesmo resultado
tetoNo
avisoNo
linhasYeslinhas pedidas no schema
schemaNoo schema com a seed fixada, só acima do teto
formatoYes
conteudoNoo arquivo gerado, como texto
acima_do_tetoNotrue quando as linhas passam do teto por chamada e nada foi gerado

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / formato / description
      Previous value: -"csv (padrão), json ou sql"New value: +"csv (padrão), json, sql ou xlsx (Excel: volta um link para baixar o arquivo, que não entra no contexto)"
    • changedInput schema / properties / formato / enum
      Previous value: -[
-  "csv",
-  "json",
-  "sql"
-]New value: +[
+  "csv",
+  "json",
+  "sql",
+  "xlsx"
+]
    • addedOutput schema / properties / link
      Added value: +{
+  "description": "só xlsx: endereço que baixa o arquivo Excel; mostre-o ao usuário sem alterar nada",
+  "type": "string"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint/openWorldHint; the description adds the real behavioral payload: the 100-row hard stop and what the response contains when it trips, the xlsx download-link special case with a handling instruction, seed determinism guarantees, and the field-by-field error shape for invalid schemas. This is information no annotation or schema conveys.

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?

Purpose is front-loaded and every sentence carries a distinct rule (row cap, fallback, xlsx link, seed, errors) with no filler. The single dense paragraph is somewhat heavy, but nothing is redundant.

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 4-parameter tool with nested schema and an output schema present, the description covers everything an agent needs to call it correctly: size limits, format-specific return behavior, seed semantics, and error handling. Return-value detail is legitimately delegated 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 the baseline is 3, but the description adds meaning beyond the schema: it explains why seed matters (identical output with the same seed and schema; a random one is drawn and returned when absent) and ties the row ceiling to the rows parameter. It adds real semantic value without documenting every field.

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?

Opens with a specific verb and resource ('Gera massa de teste a partir de um schema JSON do massa') and immediately states the output forms (csv, json, sql, xlsx link). An agent can distinguish this from importar_ddl or validar_documento without opening any schema.

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

Usage Guidelines4/5

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

Gives concrete operating conditions: up to 100 rows per call, nothing is generated above that and the response falls back to the /api/generate curl path, and xlsx bypasses the row ceiling. It does not name sibling tools (listar_tipos only appears inside the schema), so it stops just short of explicit alternative routing.

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

All massa toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources