Skip to main content
Glama

Mandate Office

by com.mandateoffice
OverviewDiscussionsAdmin

list_actions

Read-only

List the legal document actions Mandate Office offers or is preparing, with status, audience, version, last_verified and updated dates. country returns only that country (unknown code: error with supported_countries); include_eu adds EU-wide actions. Free, read-only.

Input Schema

NameRequiredDescriptionDefault
countryNoOptional ISO country code filter, e.g. ES, DE, EE, EU.
include_euNoWith country: also return EU-wide actions. Default false.
changed_sinceNoOnly actions updated on or after this date (YYYY-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / changed_since
      Added value: +{
+  "description": "Only actions updated on or after this date (YYYY-MM-DD).",
+  "type": "string"
+}
    • changedInput schema / properties / country / description
      Previous value: -"Optional ISO country code filter, e.g. ES, DE, EE."New value: +"Optional ISO country code filter, e.g. ES, DE, EE, EU."
    • addedInput schema / properties / include_eu
      Added value: +{
+  "description": "With country: also return EU-wide actions. Default false.",
+  "type": "boolean"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds useful details: it is free, unknown country codes produce an error with supported_countries, and include_eu expands results to EU-wide actions. It does not cover pagination, ordering, or result-size limits, but the added behavioral context is meaningful.

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 three tight sentences with the primary purpose and key returned fields front-loaded. The filter behavior and error condition follow without unnecessary repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only listing tool with no output schema, the description covers purpose, key filters, error behavior, and returned fields. The main remaining gap is that it does not mention pagination, ordering, or result limits if the list can be large.

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 by explaining that country returns only that country and that unknown codes error with supported_countries. include_eu is also clarified, though changed_since is left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a clear verb and resource: 'List the legal document actions Mandate Office offers or is preparing.' It specifies the returned fields, but it does not distinguish this tool from siblings like find_law or list_templates.

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

Usage Guidelines3/5

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

Usage is implied by the filtering behavior for country and include_eu, plus the note that unknown country codes error with supported_countries. However, it never states when to choose this tool over sibling tools or when not to use it.

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

All Mandate Office 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