Skip to main content
Glama
Sign In

site

by com.difcvsadgm
OverviewDiscussionsAdmin

The questions the enquiry asks

enquiry_fields

Every field of the DIFC vs ADGM enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the output contents (key, label, type, required, help text, allowed options) and notes the intended downstream use. However, it does not explicitly state that the tool is read-only, nor does it describe potential error conditions or any operational side effects. The absence of side effects is implied but not stated, leaving some ambiguity for a getter-like tool.

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?

The description is a single, compact sentence that front-loads the core purpose (listing every field) and appends a critical usage hint (keying answers). Every word contributes value, with no filler or redundancy.

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?

There is no output schema, so the description must explain the return value, which it does thoroughly by listing the field attributes. It also ties the output to the submit_enquiry workflow. For a parameterless listing tool, this is sufficiently complete; no critical information is missing.

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 has zero parameters, so schema coverage is trivially 100%. The description correctly avoids discussing parameters because none exist. Baseline for 0 params is 4, and the description adds no unnecessary parameter information.

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 states the tool returns every field of the DIFC vs ADGM enquiry with specific attributes (key, label, type, required, help text, allowed options). It clearly identifies the resource and the output. It does not explicitly name sibling checker tools, but it does mention submit_enquiry as the intended consumer, which helps distinguish it from the checker tools.

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 description explicitly instructs to pass answers to submit_enquiry keyed by field key, giving a clear usage context. It implies this tool is a prerequisite for understanding the enquiry fields before submitting answers. It does not provide exclusions or alternatives, but the single-purpose nature is clear enough.

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

All site toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources