Skip to main content
Glama
sebastienrousseau

inclusio-mcp

by sebastienrousseau
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Count registered documents

doc_count
Read-onlyIdempotent

Count documents registered in the manifest to verify server connectivity and manifest validity without transferring the full document list.

Instructions

Count the documents registered in data/meta.yaml.

    Use this as a cheap connectivity/health probe to confirm the server
    sees a valid manifest without transferring the full document list.
    When you need each document's id, class, and flags, call
    ``list_docs`` instead.

    Cheap probe for clients that just want to verify connectivity
    and that the engine sees a valid manifest.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, destructiveHint, openWorldHint. Description adds that it's a cheap probe and confirms server sees valid manifest without transferring full list. No contradictions.

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?

Very concise; uses two clear blocks. Main action front-loaded. Every sentence adds value.

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 no parameters, good annotations, and presence of an output schema, the description sufficiently covers all necessary contextual information for a simple count operation.

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?

No parameters defined; schema covers all. Baseline for 0 parameters is 4. Description does not need to add parameter detail.

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?

Description clearly states 'Count the documents registered in data/meta.yaml' with a specific verb and resource. It also distinguishes from sibling tool list_docs by noting that list_docs provides individual document details.

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

Usage Guidelines5/5

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

Explicitly states when to use: as a cheap connectivity/health probe. Also tells when not to use: if you need each document's id/class/flags, call list_docs instead.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sebastienrousseau/inclusio'

If you have feedback or need assistance with the MCP directory API, please join our Discord server