Skip to main content
Glama

Modulos AI Governance Platform

compare_with

Read-only

Returns the published comparison between Modulos and one other vendor: a row per dimension (frameworks, risk quantification, deployment, certifications, pricing and more) with the statement for each side, and the cases in which each vendor is the better choice. The comparison is written by Modulos; the page lists its sources.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "competitor": "<competitor>"
    },
    "name": "compare_with"
  }
}

Input Schema

NameRequiredDescriptionDefault
competitorYesVendor slug as returned by list_competitors, for example "credo-ai".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly and closed-world safety, so the description earns credit for the extra disclosure that the comparison is vendor-authored by Modulos and that the page lists its sources — a bias/provenance warning an agent would not otherwise have. It does not cover failure behavior for an unknown or unlisted slug.

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 return description, then the provenance caveat. The parenthetical dimension list is informative rather than filler, and nothing is repeated.

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?

With no output schema, the description carries the return-shape burden and does so: rows per dimension, statements for each side, and the win conditions for each vendor, plus the authorship disclaimer. Nothing an agent needs to call this correctly is missing.

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 coverage is 100% and the single parameter already documents the slug format with an example and the list_competitors provenance. The description only restates "one other vendor," adding no format, matching, or error 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: "Returns the published comparison between Modulos and one other vendor," then enumerates the row-per-dimension structure. This is clearly a single-vendor comparison, distinguishable from list_competitors (enumeration) and check_fit (evaluation) without opening any schema.

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 is only implied: the reader can infer the tool needs a vendor slug previously obtained from list_competitors, but the description never says when to call this versus check_fit or get_capabilities, and gives no when-not guidance.

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