Skip to main content
Glama
Sign In
@openar/mcp

@openar/mcp

Official
by openar-pt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_meta

Fetch available legislatures, parliamentary groups, and initiative types for filtering initiatives, with optional scope by legislature.

Instructions

Get available filter values: legislaturas, grupos parlamentares, tipos de iniciativa

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": "get_meta"
  }
}

Input Schema

NameRequiredDescriptionDefault
legislaturaNoFilter grupos/tipos to a specific legislatura

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A3.8/5.0
Behavior2/5

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

No annotations provided; description only states purpose without disclosing traits like read-only behavior, rate limits, or effects. Minimal behavioral info.

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?

Single sentence with key info, no redundancy, perfectly front-loaded.

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 metadata tool with one optional parameter and no output schema, the description adequately conveys the return value categories. Slightly ambiguous on response format but acceptable.

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 covers parameter fully (100% coverage), but description adds value by specifying the categories of returned filter values, which informs the parameter's filtering role.

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 'Get available filter values: legislaturas, grupos parlamentares, tipos de iniciativa' clearly states the tool fetches metadata for filtering, distinguishing it from sibling tools that retrieve specific entities.

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?

No explicit guidance on when to use versus alternatives, but the purpose is self-evident: use to obtain filter values for other tools. Implied usage, no exclusions.

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

Deploy Server

Other Tools