Skip to main content
Glama

getMyStayDetail

Read-only

Get the current title, description, listed flag and status ('Live', 'Paused' or 'Closed') for one of your Stays. A Closed Stay is read-only and cannot be edited. Call this before updateStayDetail so the agent knows the current values and doesn't accidentally overwrite them. Requires NOMADSTAYS_MCP_AGENT_TOKEN.

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": {
      "stayId": "<stayId>"
    },
    "name": "getMyStayDetail"
  }
}

Input Schema

NameRequiredDescriptionDefault
stayIdYesThe Stay's EntryID (use getMyStays to find it)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower; the description adds auth requirements (NOMADSTAYS_MCP_AGENT_TOKEN), the read-only consequence of Closed status, and the intended sequencing before a mutation. It does not discuss pagination or error behavior, but those are minor for a single-record fetch.

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, front-loaded with what is returned, then the state caveat, then the sequencing advice and token requirement. Every sentence carries distinct information with no repetition of the title or annotations.

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 read tool with no output schema, the description pre-emptively enumerates the returned fields and status values, and flags the token requirement, which is enough for correct invocation. Missing only edge-case behavior such as what happens for a nonexistent or unauthorized stayId.

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 coverage is 100% and the sole parameter stayId is fully described in the schema, including how to obtain it via getMyStays. The description contributes only the possessive framing ('your Stays') and adds no format or validation detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb (get) and resource (a single Stay), and enumerates exactly what is returned: title, description, listed flag, and status with its enumerated values ('Live', 'Paused', 'Closed'). The singular scope ('one of your Stays') distinguishes it from the listing sibling getMyStays without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use guidance: call this before updateStayDetail so current values are known and not accidentally overwritten. It also states a when-not condition implicitly, that a Closed Stay is read-only and cannot be edited, which tells the agent the update path is blocked in that state.

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.