Skip to main content
Glama

Aurinia — book across venues via your AI assistant

get_provider_info

Read-only

Details for one venue by provider_id: id, type (doctor/hostel), name, city, address. Read-only, no auth. Use it to confirm a venue before get_availability / book.

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": {
      "provider_id": "<provider_id>"
    },
    "name": "get_provider_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
provider_idYesVenue id as returned by find_providers (e.g. rudko-vertebrolog).

Output Schema

NameRequiredDescriptionDefault
idYes
cityNo
nameYes
typeYesdoctor | hostel
addressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / provider_id / description
      Added value: +"Venue id as returned by find_providers (e.g. rudko-vertebrolog)."
  2. Changed1 schema field changed
    • changedOutput schema / properties / type / description
      Previous value: -"doctor | hostel | spa"New value: +"doctor | hostel"
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "address": {
      +      "type": "string"
      +    },
      +    "city": {
      +      "type": "string"
      +    },
      +    "id": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "type": {
      +      "description": "doctor | hostel | spa",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "type",
      +    "name"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this while adding genuinely new context: 'no auth' tells the agent the call needs no credentials, which the structured fields do not say. It does not cover failure behavior for an unknown provider_id, but the added auth guarantee is real value beyond annotations.

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 compact sentences: the resource and returned fields come first, then the safety/auth profile, then the workflow pointer. No filler and nothing buried.

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

Completeness5/5

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

For a single-parameter read lookup with an output schema, the description covers purpose, key, returned fields, auth requirements, and sequencing relative to get_availability and book. Nothing an agent needs in order to call it correctly is missing.

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 provider_id property already carries a description plus a concrete example (rudko-vertebrolog). The prose only restates that the lookup is keyed by provider_id, adding little beyond the schema, so 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 and resource ('Details for one venue by provider_id') and enumerates the fields returned (id, type, name, city, address), including the doctor/hostel type distinction. An agent can separate this lookup from get_availability or book without opening the schema.

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?

Explicitly states the workflow position: 'Use it to confirm a venue before get_availability / book,' naming two siblings and the condition that selects this one. It stops short of stating when not to use it (e.g., bulk discovery should go to find_providers), so it is not fully exhaustive.

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