Skip to main content
Glama
Sign In
convergeqa-mcp

convergeqa-mcp

Official
by convergeqa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

convergeqa_iterate_templates

List ConvergeQA API-visible templates for multi-model document review using configured credentials.

Instructions

List API-visible ConvergeQA templates for the configured credential.

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

Input Schema

NameRequiredDescriptionDefault
outputNo
base_urlNoConvergeQA base URL.https://convergeqa.net
api_key_envNoUppercase environment variable name containing a ConvergeQA Developer API key.CONVERGEQA_API_KEY
credential_kindNoauto
redact_private_urlsNo
service_account_key_envNoUppercase environment variable name containing the ConvergeQA service-account key.CONVERGEQA_SERVICE_ACCOUNT_KEY

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so description should disclose behavioral traits. It only states a basic action without mentioning side effects, permissions, or what 'API-visible' entails.

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?

Single sentence with no fluff, front-loaded with the core action. Efficiently communicates the purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 6 parameters, no output schema, and many sibling tools, the description is too sparse. It omits how templates relate to other tools, output format, or any configuration details.

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

Parameters2/5

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

Schema coverage is 50%, but description adds no meaning to parameters like 'output' or 'redact_private_urls'. It does not compensate for the undocumented parameters.

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?

The description clearly states the verb 'List', the resource 'ConvergeQA templates', and the scope 'API-visible for the configured credential', which is specific and distinct from sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus siblings like convergeqa_iterate_session or convergeqa_iterate_start. Missing context for selecting this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools