Skip to main content
Glama

About IVERIOS

about_iverios
Read-onlyIdempotent

Information about IVERIOS and IVERIOS Trust Center: what it is, how vendors publish a trust center and how customers (assessors) use it — access requests, NDA, questionnaires, AI assistants — plus pricing, FAQ and the other IVERIOS tools. No sign-in needed.

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

Input Schema

NameRequiredDescriptionDefault
topicNoOptional section; omit for everything

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds context beyond them: no authentication is required and omitting the topic argument returns the complete content set. It does not state the response format (prose/markdown) despite having no output schema, which is the one remaining behavioral gap.

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?

It is a single sentence, front-loaded with the subject ('Information about IVERIOS and IVERIOS Trust Center') and then listing coverage via a parenthetical aside. The em-dash clause runs long, but every clause maps to actual content sections rather than filler.

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?

For a low-complexity, zero-required-parameter, read-only informational tool with annotations covering safety and a fully documented schema, this is close to sufficient. An agent knows what it returns conceptually and that no auth is needed; only the concrete return format is left unstated.

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 enum parameter is fully documented in the schema, including 'omit for everything', so a baseline of 3 applies. The description loosely maps its prose topics onto the enum values (for_vendors, for_assessors, pricing, faq, products), which helps an agent pick a section, but it does not name or explain the less obvious 'connect' value.

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?

The description names a specific resource (IVERIOS / IVERIOS Trust Center documentation) and enumerates the covered subject matter: vendor publishing flow, assessor usage, access requests, NDA, questionnaires, AI assistants, pricing, FAQ, and the other IVERIOS tools. That is far more specific than 'about', though it does not explicitly contrast itself with adjacent siblings such as get_overview or get_privacy, which an agent could easily confuse with the 'overview' topic here.

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?

It provides one genuinely useful operational condition — 'No sign-in needed' — which tells an agent this is callable before authentication. However, there is no explicit when-to-use-versus-alternatives guidance: nothing says whether to prefer get_overview or get_privacy over this tool, or to call this first to discover the other tools.

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