Skip to main content
Glama

muninn_table_define

DestructiveIdempotent

Declare a table (a kind of thing you want to track — Staff, Sources, Clients) and the fields its records share. Re-calling with the same slug UPDATES the definition: fields you pass replace the current set, so send the whole list, not a delta. Field key is permanent and is what record values are stored under; label is what a human sees and can be renamed freely. Mark a field private:true to keep it out of the grid, out of csv/xlsx export, and out of any team-shared view — private values never leave the encrypted record body. Field types: text, textarea, number, date, select, multi-select, checkbox, nested-table. Use textarea for anything that runs to more than a line — notes, a description, an address, a bio: it stores exactly like text and tells the app to give it a multi-line box instead of a single-line input.

Input Schema

NameRequiredDescriptionDefault
titleYesHuman-readable name, e.g. 'Staff'. Renameable.
fieldsYesThe full field list, in display order. Replaces any existing definition.
tableSlugYesStable identifier, e.g. 'bui-staff'. Permanent — this is how records are filed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond annotations: explains that re-calls replace (not merge) fields, that `key` is permanent and orphaning risk, that `label` is freely renameable, and precisely what private:true excludes (grid, csv/xlsx export, team views, and that values stay in the encrypted body). This is rich behavioral context annotations alone don't convey.

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?

Dense and front-loaded with the update semantics early. Slightly long, especially the trailing textarea explanation and field-type enumeration, but every sentence carries useful information.

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?

A mutation tool with no output schema, yet the description fully covers replacement behavior, permanence rules, privacy effects, and field type options — everything an agent needs to invoke it correctly.

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%, but the description adds real meaning — permanence of key vs renameability of label, the private flag's downstream effects, and practical guidance on textarea vs text (multi-line box, same storage). Adds value beyond the schema's own descriptions.

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 (Declare) plus resource (a table) and its fields, with concrete examples (Staff, Sources, Clients). Clearly distinguishable from siblings like muninn_table_record_add or muninn_table_list.

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?

Explicitly documents the critical re-call semantics: calling with the same slug UPDATES the definition and fields replace the current set, so send the whole list not a delta. This is strong when-to/behavioral guidance, though it doesn't contrast with sibling tools like delete or list.

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