Skip to main content
Glama
Sign In

Fortunest demo

by ai.fortunest
OverviewDiscussionsAdmin

Docs sections

docs_lookup
Read-onlyIdempotent

DEMO portfolio (synthetic, shared, read-only). Read one to five exact section labels from the product docs index; missing sections are reported rather than fabricated.

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": {
      "labels": "<labels>"
    },
    "name": "docs_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, closed-world and non-destructive, so the safety profile is fully declared. The description adds genuinely non-obvious behavior: the data is synthetic/shared, and unknown labels come back as reported misses instead of fabricated content, which changes how an agent should interpret a response. It stops short of describing the return shape, but that is a minor omission.

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?

Two compact clauses with no filler, and the operational constraint (exact labels, misses reported) is front-loaded. The leading 'DEMO portfolio (synthetic, shared, read-only)' is useful context but slightly telegraphic about what it has to do with a docs index.

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 one-parameter, no-output-schema read tool, the description supplies the essential behavior an agent needs: exact-label semantics, the 1-5 bound, and the no-fabrication guarantee. Missing only return-format and matching-rule details, which are secondary at this complexity.

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?

Schema coverage is 0% and the single parameter is just an array of strings, so the description carries the load: it explains the items are exact section labels, that between one and five are allowed, and that unmatched labels are surfaced rather than invented. That is meaningful semantics beyond the bare array type, though it does not say whether matching is case-sensitive.

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?

States a specific verb and resource: 'Read one to five exact section labels from the product docs index.' That is clearly a lookup-by-key operation, distinguishable in spirit from a search tool, though the description never names docs_search so the agent must infer the contrast. The scope is precise enough to act on.

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?

The word 'exact' plus 'missing sections are reported rather than fabricated' implicitly tells the agent this is for when the label is already known, but it never states that explicitly or points to docs_search for the discovery case. Usage is implied rather than stated, which is the definition of a minimum-viable score here.

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

All Fortunest demo 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