Skip to main content
Glama

Chinng AI-Agent Portal

portal_list_government

List official government documents without their Markdown bodies.

Use country (for example "us", "jp", or "eu") and source to narrow results. Federal Register document types include "Rule", "Proposed Rule", and "Notice"; Japanese RSS sources use their configured update class as document_type. EU sources cover EUR-Lex legislation and case-law (document_number carries the CELEX number) and European Commission press releases. Call portal_get for a selected id when its full portal record is needed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "portal_list_government"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNo
untilNo
offsetNo
sourceNo
countryNo
document_typeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and usefully discloses that Markdown bodies are omitted and that full records require portal_get. It also explains source-specific document_type behavior, but leaves pagination, default limits, and date-filter semantics unstated.

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?

The purpose is front-loaded and the examples earn their place by clarifying ambiguous source-specific document_type values. The EU sentence is dense but relevant, and there is no redundant restatement.

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?

For a 7-parameter, unannotated list tool, the description covers purpose, filtering, document-type nuances, and the portal_get handoff, while relying on the output schema for return shape. It remains incomplete because date-range and pagination parameters are not explained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 7 parameters and 0% description coverage, so the description must compensate. It explains country examples, source filtering, and document_type values for Federal Register, Japanese RSS, and EU sources, but says nothing about limit, offset, since, or until.

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 opening sentence gives a specific verb and resource, 'List official government documents', and immediately scopes the result by excluding Markdown bodies. This distinguishes the tool from portal_get, which is described as returning the full portal record.

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?

It explicitly says to use country and source to narrow results and routes full-record needs to portal_get for a selected id. It does not explain when to prefer portal_search or generic portal_list over this government-specific 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