Skip to main content
Glama
Sign In

Dubai Diligence

by io.github.stevenworlow
OverviewDiscussionsAdmin

Fetch a Dubai Diligence document

fetch
Read-only

The full registered figures behind one search result, as text, with the canonical URL to cite.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAn id returned by search, which is the page path, for example '/areas/dubai-marina'.

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint annotation already tells the agent this is a safe read. The description adds some useful context (it returns text rather than structured data, and includes a canonical URL for citation), which is valuable for an agent that has to quote or cite the result. It does not say anything about pagination, size limits, or what happens when the id does not exist.

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, tight sentence with no padding, and the key facts (full data, one result, text output, citable URL) come first. It feels a little noun-heavy and would benefit from an explicit verb, such as 'Fetch', but this is minor.

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?

The tool has a single fully documented parameter, a readOnlyHint, and an output schema, so the description's remaining job is to explain purpose and return shape; it does both. The only missing piece is an error or not-found note, which is minor given the overall richness of the structured data.

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?

There is a single parameter (id), and its schema description already documents its 100% coverage (for example, '/areas/dubai-marina'). The description does not tell the agent anything about the id, such as its source or format, so the baseline 3 applies.

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 says the tool returns 'the full registered figures behind one search result, as text, with the canonical URL to cite', which makes the fetched resource (one search result's full record) clear and sets it apart from the search sibling. It omits an explicit verb, but the noun phrase is unambiguous enough to compensate.

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?

'Behind one search result' implies the tool is used after a search and on a single result, and the schema's id description reinforces that the id comes from search. There is no explicit statement of when not to use it, nor of alternatives such as search for multi-result queries, so the guidance is only implied.

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

All Dubai Diligence 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