easyjur_api_status
Read-onlyIdempotent
Status da API EasyJur do escritório autenticado (identidade + limites).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | No |
EasyJur
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.8/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful context beyond those annotations by specifying that the status includes identity and limits for the authenticated office. No contradiction exists.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that directly conveys the tool's purpose and scope. There is no padding, redundancy, or unnecessary detail.
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?
The tool appears simple and annotations cover safety and idempotency, but there is no output schema and the optional query parameter is completely undocumented. The description gives the core idea but does not fully explain request usage or return-format expectations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has one optional 'query' object with no property descriptions and schema description coverage is 0%. The description provides no information about what this query object should contain or how it affects the request, leaving the agent without meaningful parameter semantics.
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?
The description clearly states that the tool reports the API status of the authenticated EasyJur office, with identity and limit information. This is specific about the resource (EasyJur API status for the authenticated office) and distinguishes it from sibling tools like easyjur_get_token or easyjur_get_user.
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?
The description provides clear context: use this tool to check the API status, identity, and limits of the authenticated office. It does not explicitly mention when not to use it or name alternatives, but the intended use is clear enough for a status-check tool.
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.
TDQS
C2.8/5.0
Disambiguation5/5
Each tool targets a distinct resource or sub-resource with clear CRUD actions. The easyjur_ tools are separated by entity (agenda, processo, pessoa, etc.) and by action (create, get, list), while sub-resource tools like easyjur_processo_partes or easyjur_agenda_comentarios have unambiguous scopes. Platform tools (authenticate, connect, marketplace) serve disjoint meta-purposes, so no ambiguity.
Naming Consistency3/5
Most easyjur_ tools follow a consistent verb_noun pattern (create_agenda, get_processo, list_despesas), but several break it with noun_subresource names (easyjur_agenda_comentarios, easyjur_processo_financeiros) and the platform tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) use plain nouns without the prefix. This mixture of conventions makes the set less predictable.
Tool Count2/5
47 tools is well above the threshold for a focused MCP server, even for a comprehensive legal management domain. The inclusion of platform meta-tools inflates the count, and many entities (agenda, processo) have multiple sub-resource readers. This volume risks overwhelming agents and slowing tool selection.
Completeness2/5
The tool surface provides create, get, and list for each entity, but there are no update or delete operations for any entity. Sub-resources (documentos, partes, mensagens, etc.) are read-only. The only workaround mentioned is creating agenda items to record movements, which is a workaround, not a real update. This is a significant gap that will cause dead ends for workflows requiring modification or removal.