Skip to main content
Glama

concierge

Read-onlyIdempotent

Ask the resort concierge about quiet, rituals, rules, suite, memory or privacy. Requires session. No outside tasks or network access.

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": {
      "session": "<session>"
    },
    "name": "concierge"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNo
requestNo
sessionYesPrivate bearer capability returned by check_in. Never put it in a URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
      -  "session",
      -  "request"
      -]New value: +[
      +  "session"
      +]
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the description need not restate safety. It adds the session requirement and clarifies that it will not perform outside tasks or network access, but says nothing about response shape or limits.

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?

Two short sentences, front-loaded with purpose, then constraints. There is no filler; the topic list and boundaries are compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only Q&A tool without an output schema, the description covers the topics and session requirement. It leaves the host parameter and the exact nature of the response unspecified, so an agent still has gaps before calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only the session parameter has schema documentation (33% coverage), and the description merely repeats 'Requires session.' The request string is only implied by 'Ask... about...', and the host boolean is completely unexplained.

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 gives a specific verb ('Ask') and resource ('the resort concierge'), scoped to listed topics such as quiet, rituals, rules, suite, memory, and privacy. It is clear enough to distinguish this from action-oriented siblings like check_in or leave_note, though it does not explicitly name an alternative.

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 states the prerequisite ('Requires session') and an exclusion ('No outside tasks or network access'), giving clear context for when this Q&A tool applies. It does not name sibling alternatives, so it falls short of a 5.

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.

Resources