Obtém todos os IDs e configurações da conta (usuários, origens, tipos de tarefa, fases, tipos de processo). Use para descobrir os IDs exigidos por create/update.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark as readOnly, idempotent, non-destructive. The description adds value by specifying exactly what data is retrieved (all IDs and settings categories), expanding beyond annotation metadata with useful behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences, front-loaded with purpose and usage, no filler or repetition. Highly efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers purpose and content adequately, but lacks clarity on the query parameter and return format (no output schema). For a config lookup with one optional filter, it is minimally viable but leaves the agent unsure about filtering or result structure.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the description does not mention the optional 'query' parameter at all. With 0 params required and a flexible object type, the agent receives no guidance on how to use the query filter, creating a significant gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool fetches all account IDs and settings, listing specific categories (users, sources, task types, phases, process types). This specific verb+resource+scope distinguishes it from sibling list tools that return individual entities.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly advises usage to 'discover the IDs required by create/update', giving clear when-to-use guidance. It does not state exclusions, but the context of sibling tools makes its purpose clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The advbox_* tools are clearly distinct by resource (customer, lawsuit, transaction, post, movement) and action (create, get, list, update). Overlapping tools like lawsuit_history, lawsuit_movements, and last_movements have clear scoping in descriptions. The platform tools (authenticate, connect, marketplace) are separate and well-defined.
The advbox_* tools follow a consistent verb_noun pattern (create_customer, get_lawsuit, list_transactions). The non-advbox tools (authenticate, connect, marketplace) use different naming but are auxiliary and have clear names. Minor deviation but overall predictable.
With 26 tools, the set is on the heavy side, but the legal practice domain is broad, covering customers, lawsuits, transactions, posts, and movements, plus platform management tools. Each tool has a defined role, though some could be consolidated (e.g., the multiple movement-related list tools).
Core workflows for customers, lawsuits, and transactions are covered with create/get/list/update, but there are missing operations: no update_customer, no deletes for any resource, no get_post or update_post despite list and create. The settings tool helps discover IDs, but the lifecycle is incomplete.