Skip to main content
Glama

Contact the Docuflex team

request_access

Send a message to the Docuflex team (commercial terms, higher limits, questions). Only when the user explicitly asks and provides their own email. Limited to 5 per hour per IP.

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": {
      "name": "<name>",
      "email": "<email>",
      "message": "<message>"
    },
    "name": "request_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
emailYes
companyNo
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations present, the description carries the full behavioral burden, and it does disclose two important non-obvious traits: the 5-per-hour-per-IP rate limit and the consent precondition that the email must be the user's own. It does not say what happens after submission (confirmation, response time, whether the message reaches a human queue), which is the 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, each earning its place: what it does, when it may be called, and the hard rate constraint. The purpose and the usage gate are front-loaded ahead of the operational limit.

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 four-parameter outbound-contact tool with no annotations and no output schema, the description covers purpose, consent conditions, and rate limiting. The missing pieces are the meaning of the name/company fields and the post-submission outcome, both minor relative to the constraints already stated.

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 0%, so the description must compensate, and it partially does by clarifying that the email must be the user's own address and that the message is a free-text note to the team. It says nothing about the name or company fields, leaving two of four parameters to be inferred from their names alone.

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 uses a specific verb plus resource ("Send a message to the Docuflex team") and enumerates the intended subjects (commercial terms, higher limits, questions), which makes the intent unmistakable. It does not explicitly contrast itself with the envelope-related siblings, but the outbound-contact framing is distinctive enough that confusion is unlikely.

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?

It gives an explicit gating condition: use "Only when the user explicitly asks and provides their own email," which is far stronger than typical implied-usage guidance. The main gap is that it names no alternative route for cases outside that gate (e.g., where to look for commercial info instead).

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