Skip to main content
Glama

Modulos AI Governance Platform

get_capabilities

Read-only

Returns structured facts about the Modulos AI Governance Platform: company, what the platform is for, the supported regulations and standards with requirement and control counts, integrations, deployment options and data location, certifications, indicative pricing and key links. Use this to decide whether Modulos belongs on a vendor shortlist.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered. The description adds only mild behavioral context: results are "structured facts" (a static snapshot, no arguments) and pricing is "indicative," a useful caveat about precision. It says nothing about freshness/staleness of the data, response size, or rate limits.

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?

Two sentences, front-loaded with the verb and subject, and the long enumeration is a single dense list rather than padding. The closing sentence supplies the decision purpose instead of restating the contents.

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?

With no parameters and no output schema, the description carries the burden of telling the agent what comes back, and it does so by enumerating the fact categories (regulations with counts, certifications, pricing, links). Missing only a note on data currency and how it differs from the overlapping info/evidence siblings.

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 takes zero parameters, so the baseline is 4 and there is nothing for the description to compensate for. The enumeration of returned fact categories is helpful framing but concerns output, not inputs.

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?

Opens with a specific verb+resource ("Returns structured facts about the Modulos AI Governance Platform") and enumerates the fact categories returned: company, purpose, regulations with requirement/control counts, integrations, deployment, certifications, pricing, links. That is far more than a restated name, though it never distinguishes itself from siblings such as get_modulos_info or get_trust_evidence that plausibly overlap.

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?

Gives an explicit decision context — "Use this to decide whether Modulos belongs on a vendor shortlist" — which tells the agent the moment this tool is appropriate. It stops short of exclusions or naming alternatives (e.g., when to prefer check_fit or get_trust_evidence), so an agent facing overlapping siblings still has to guess.

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