Skip to main content
Glama

Aurinia — book across venues via your AI assistant

find_providers

Read-only

Find a venue in the Aurinia network. Venue types currently bookable: doctor, hostel. Optional: query (e.g. 'vertebrologist'), city, type. Returns a providers array; use a provider_id from it for get_availability / book.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity name, Latin or Cyrillic (e.g. Chernivtsi, Чернівці).
typeNoVenue type: doctor | hostel.
queryNoFree text: specialty, service or need, in English or Ukrainian (e.g. 'back pain', 'dorm bed', 'вертебролог'). May include the city.

Output Schema

NameRequiredDescriptionDefault
providersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / city / description
      Added value: +"City name, Latin or Cyrillic (e.g. Chernivtsi, Чернівці)."
    • addedInput schema / properties / query / description
      Added value: +"Free text: specialty, service or need, in English or Ukrainian (e.g. 'back pain', 'dorm bed', 'вертебролог'). May include the city."
    • addedInput schema / properties / type / description
      Added value: +"Venue type: doctor | hostel."
    • addedInput schema / properties / type / enum
      Added value: +[
      +  "doctor",
      +  "hostel"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / properties / providers / items / 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": {
      +    "providers": {
      +      "items": {
      +        "properties": {
      +          "address": {
      +            "type": "string"
      +          },
      +          "city": {
      +            "type": "string"
      +          },
      +          "id": {
      +            "description": "provider_id for other tools",
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "type": {
      +            "description": "doctor | hostel | spa",
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "providers"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-network behavior are covered structurally. The description adds that a providers array is returned and that provider_id feeds downstream tools, but says nothing about empty-result behavior when no filters are supplied, result limits, or ordering.

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?

Four short clauses, front-loaded with the purpose, then scope, then parameters, then the downstream handoff. No filler or restatement of the title; every sentence carries distinct information.

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?

With an output schema available, annotations covering read-only and open-world behavior, and 100% schema description coverage, the description need only establish the discovery role and the follow-up call, which it does. The remaining gap is unspecified behavior when all filters are omitted.

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 100%, so the baseline is 3, but the description adds genuine meaning with "Venue types currently bookable," implying the doctor/hostel enum is a current subset rather than a permanent domain. It also labels the three inputs as optional and reinforces the query semantics with a concrete example matching the schema's own examples.

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 opens with a specific verb and resource: "Find a venue in the Aurinia network," and immediately narrows scope with "Venue types currently bookable: doctor, hostel." It is clearly a discovery/search tool, distinguishable from siblings like book or get_availability, though it never names those alternatives explicitly as the tool it is not.

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?

Usage context is clear: this is the entry point of a booking flow, and "use a provider_id from it for get_availability / book" tells the agent exactly what to do next. There are no explicit when-not-to-use statements or contrast with get_provider_info for direct lookups, so it stops short of full routing guidance.

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