Skip to main content
Glama
Sign In
qune-tech/ocds-mcp

qune-tech/ocds-mcp

by qune-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

get_index_info

Retrieve combined statistics for release, embedding, and company profile counts to verify API connectivity and assess available data.

Instructions

Get combined statistics: release and embedding counts from the REST API, plus local company profile counts. Call this first to check connectivity and see what data is available.

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_index_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates a read operation and mentions data sources (REST API, local), but does not disclose potential side effects, authentication needs, or rate limits. It is moderately transparent.

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 two sentences, front-loaded with the core purpose, and every sentence adds value. No unnecessary words.

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

Completeness5/5

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

Given the context of zero parameters, no output schema, and many sibling tools, the description fully explains what the tool does and its role as an initial connectivity and data availability check. It is complete and appropriately scoped.

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?

The tool has zero parameters, so schema coverage is 100%. The description does not need to add parameter details, and it appropriately adds value by explaining what the tool returns and its purpose.

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 the verb 'Get' and the resource 'combined statistics', detailing what is included: release and embedding counts plus local company profile counts. It distinguishes itself from sibling tools which are CRUD operations on 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 Guidelines4/5

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

The description explicitly advises to call this tool first to check connectivity and see available data, providing clear guidance on when to use it. While it doesn't mention when not to use it or name alternatives, the usage context is well defined.

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