Skip to main content
Glama
Sign In

Passage Data — cited environmental limits

by io.github.kedu21-beep
OverviewDiscussionsAdmin

Create a site

create_site

A new site in the account, with its name only: it is placed on a map later, on its page. Each call makes one more site, so look for the site with list_sites first.

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>"
    },
    "name": "create_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe site's name, as its people call it (a mine, a plant, a project).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the safety profile (not read-only, not destructive, not idempotent, closed-world). The description adds real context beyond that: only a name is set at creation and map placement happens later on the site's own page. It reinforces non-idempotency ('each call makes one more site'), which annotations already signal, so it edges just below the top.

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 tight sentences with no waste; the scope constraint ('name only') and the list_sites routing are both front-loaded. The first sentence reads as a fragment, a minor structural blemish.

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 creation tool with full schema coverage and annotations covering the safety profile, the description supplies what is needed to call it correctly. No output schema exists, so return values need not be described; duplicate-handling behavior is the only notable omission.

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 100% and the single 'name' parameter is already fully documented in the schema. The phrase 'with its name only' confirms that no other fields are provided, which adds slight value but no syntax or format detail beyond the schema. 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 conveys creation of a new site in the account and implies a verb (a new site is made per call). It contrasts with list_sites as the lookup tool. It stops short of a crisp 'Creates a...' opener but the resource and action are unambiguous.

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 explicitly directs the agent to check list_sites first before creating, which is clear contextual guidance. It does not state when creation is inappropriate or what happens on duplicate names, so it is not full when/when-not coverage.

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

All Passage Data — cited environmental limits 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