Skip to main content
Glama

Modulos AI Governance Platform

get_trust_evidence

Read-only

Returns security and compliance evidence for vendor due diligence: certifications, data location, the documents in the Modulos trust center with their access level, subprocessors and where they hold data, and recent trust updates. Document files are requested by a person at https://www.modulos.ai/trust/.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/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 a genuinely useful constraint beyond them: document files are not returned and must be requested from a person via the trust page URL. That prevents an agent from promising downloads it cannot deliver. It does not cover auth requirements or freshness of the evidence, keeping it below a 5.

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 resource and its contents, followed by the one caveat that changes agent behavior (files require a human request). The enumerated list is dense but every item carries retrieval meaning, so nothing is padding.

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 parameters, no output schema, and a read-only annotation profile, this is a low-complexity tool whose description nonetheless covers the returned fields and the file-access limitation. An agent has everything needed to call it correctly and set expectations for the caller.

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 of 4 applies; there is nothing for the description to compensate for. The schema is empty and fully consistent with the description's framing as a single fixed evidence snapshot.

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 security and compliance evidence") and enumerates exactly what evidence is returned: certifications, data location, trust-center documents with access level, subprocessors, and recent updates. That enumeration cleanly separates it from capability/knowledge/competitor siblings without needing to name them.

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 phrase "for vendor due diligence" gives the agent a clear situational trigger for selecting this tool over get_capabilities or get_knowledge. It stops short of explicit exclusions or naming an alternative when the agent needs something else, so it is context without routing rules.

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