Skip to main content
Glama

Modulos AI Governance Platform

check_fit

Read-only

Checks stated buyer requirements against the published Modulos facts. Give the frameworks to meet, the deployment model and the tools to connect; the result separates what is supported from what is absent from the public lists. Nothing in the request is stored.

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

Input Schema

NameRequiredDescriptionDefault
industryNoIndustry of the buyer, for example "Insurance".
deploymentNoDeployment model the buyer requires.
frameworksNoRegulations or standards the buyer must meet, for example ["EU AI Act", "ISO 42001", "DORA"].
integrationsNoTools the buyer wants connected, for example ["Jira", "GitHub", "Snowflake"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds real value beyond them: the result separates supported from absent items (important since there is no output schema) and it discloses that nothing in the request is stored. It does not cover latency, rate limits, or what the unsupported output looks like in detail, so it is strong but not exhaustive.

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?

Three short sentences, front-loaded with the core action, then the input expectation, then the output nature. Slight redundancy between the first and third sentences, but nothing is wasteful.

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 output schema and no required parameters, the description usefully characterizes the return value as a supported/absent split and reassures on data retention. It leaves open what happens with an empty request and how partial matches are reported, but it is sufficient to call the tool correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so all four parameters including the deployment enum are already documented. The description restates frameworks, deployment and tools at a high level and omits 'industry' entirely, adding little semantics beyond the schema — baseline 3 applies.

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?

States a specific verb and resource: checking buyer requirements against published Modulos facts, with the input shape (frameworks, deployment, tools) implied. It is clearly a fit/gap check rather than a listing tool like get_capabilities, though it never explicitly contrasts itself with that sibling.

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?

Usage context is implied by 'Checks stated buyer requirements' — you call it when you have requirements to validate — but there is no explicit when-not guidance and no named alternative for related queries such as capability lookup or competitor comparison.

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