Skip to main content
Glama
Sign In

Maplith

by com.maplith
OverviewDiscussionsAdmin

Object detail

get_object
Read-only

Read one object before you act on it: its applicable decision statements, fields, relations and caveats. Use this, not fetch, for an object you can name; route for the path between two objects; ask when the question spans several. Rules come as trees: each has a layer (principle, policy, rule, default) and rests_on the principle above it; full and compact rules carry statement keys and coverage, and statement_key fetches a compact rule in full. The detail also carries aliases, row_count and row_count_details, grain, field_id, also_called, recognised_by, auto_detected, role and role_basis, count-only profiles, personal-data classifications and pii flags, source systems and same_source_as peers, relations with join keys, coverage sides and basis (declared with declared_by, measured or guessed; null when unknown), findings and automations (list_automations has them all). Never echo pii=true values unless the task requires it. Full semantics: maplith://docs/mcp.

Input Schema

NameRequiredDescriptionDefault
nameYesObject name as the map spells it — the name search, route and the object pages hand out, e.g. "invoice" or "Invoice". A name written entirely in lower case is matched too.
contextNo{"client": "<company>"} (never a person): adds its confirmed variation.
rule_nodeNoOne rule group, by node_key.
statement_keyNoRead one applicable rule in full.
statements_onlyNoRules alone, {} when none apply; call again with it only when your client cut a long answer.
statements_queryNoRank rules; never filter them.
statements_cursorNoNext page; keep the same query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "{\"client\": \"<company>\"} (never a person): adds its confirmed variation.",
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / statements_only / description
      Previous value: -"Rules without other context."New value: +"Rules alone, {} when none apply; call again with it only when your client cut a long answer."
  3. Changed1 schema field changed
    • addedInput schema / properties / rule_node
      Added value: +{
+  "description": "One rule group, by node_key.",
+  "maxLength": 32,
+  "type": "string"
+}
  4. Changed4 schema fields changed
    • addedInput schema / properties / statement_key
      Added value: +{
+  "description": "Read one applicable rule in full.",
+  "maxLength": 80,
+  "type": "string"
+}
    • addedInput schema / properties / statements_cursor
      Added value: +{
+  "description": "Next page; keep the same query.",
+  "maxLength": 512,
+  "type": "string"
+}
    • addedInput schema / properties / statements_only
      Added value: +{
+  "description": "Rules without other context.",
+  "type": "boolean"
+}
    • addedInput schema / properties / statements_query
      Added value: +{
+  "description": "Rank rules; never filter them.",
+  "maxLength": 300,
+  "type": "string"
+}
  5. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Object name, e.g. \"invoice\""New value: +"Object name as the map spells it — the name search, route and the object pages hand out, e.g. \"invoice\" or \"Invoice\". A name written entirely in lower case is matched too."
  6. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, but the description adds substantial behavioral context beyond that: the rule-tree structure with layers and rests_on, statement_key expansion, truncation recovery via statements_only, and a real safety constraint to never echo pii=true values. This is genuine added value, not restatement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and no sentence is pure filler, but the long field-name enumeration ('aliases, row_count, row_count_details, grain, field_id, also_called...') is a dense wall that is hard to parse and would read better as structured bullets. Detail is warranted by tool complexity but organization suffers.

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?

Complex tool with 7 params and no output schema, yet the description enumerates what the detail carries (rules, relations with join keys, coverage, PII flags, findings, automations) and points to a full-semantics doc. An agent has enough to call it correctly and interpret the return.

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 real meaning: statement_key 'fetches a compact rule in full', statements_query 'ranks rules; never filter them', and statements_only re-call behavior on truncated answers. These semantics go beyond the schema descriptions, warranting 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 and resource ('Read one object') and immediately scopes what the detail contains: decision statements, fields, relations, caveats. It explicitly distinguishes itself from siblings ('not fetch', 'route for the path', 'ask when the question spans several'), so an agent can select it without opening other schemas.

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?

Explicit when-to-use and when-not-to-use guidance naming three alternatives (fetch, route, ask). The opening 'before you act on it' plus the routing rules leave nothing to inference about which tool to pick.

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

All Maplith toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources