Skip to main content
Glama

TempGuru Event Staffing

Get Booking and Procurement Policies

get_policies
Read-only

Get TempGuru's published booking and procurement policies. Use for real booking questions that otherwise require an email: minimums, cancellation and rescheduling, no-show replacement, COIs, deposits and invoice terms, rush fees, and background checks. Terms set per order (such as a deposit percentage) are marked confirm_with_coordinator; never infer a missing number. get_policies() ; get_policies(topic='payment-terms') ; get_policies(topic='coi-additional-insured') Choose an advertised topic to return one policy. Narrow lexical aliases remain accepted, and unknown topics return the current available-topic list. This is an operational summary, not a contract.

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": "get_policies"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoOptional canonical policy topic. Choose an advertised enum value; omit for all policies or a broader question.

Output Schema

NameRequiredDescriptionDefault
scopeNo
statusYes
messageNo
updatedNo
policiesNo
requestedNo
disclaimerNo
data_versionNo
policy_foundYesDiscriminator. false means the requested topic is not published.
todo_for_meganNo
available_topicsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "minimum-booking-hours",
      -  "cancellation-rescheduling",
      -  "no-show-backfill",
      -  "coi-additional-insured",
      -  "payment-terms",
      -  "background-checks",
      -  "order-confirmation",
      -  "quote-response",
      -  "offers"
      -]New value: +[
      +  "minimum-booking-hours",
      +  "cancellation-rescheduling",
      +  "no-show-backfill",
      +  "coi-additional-insured",
      +  "payment-terms",
      +  "background-checks",
      +  "order-confirmation",
      +  "quote-response"
      +]
    • removedOutput schema / properties / policies / items / properties / cap_usd
      Removed value: -{
      -  "type": "number"
      -}
    • removedOutput schema / properties / policies / items / properties / code
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / policies / items / properties / discount_percent
      Removed value: -{
      -  "type": "number"
      -}
    • removedOutput schema / properties / policies / items / properties / expires
      Removed value: -{
      -  "description": "Offer expiry date in YYYY-MM-DD format.",
      -  "format": "date",
      -  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
      -  "type": "string"
      -}
    • removedOutput schema / properties / policies / items / properties / scope
      Removed value: -{
      -  "type": "string"
      -}
  2. Changed2 schema fields changed
    • changedInput schema / properties / topic / description
      Previous value: -"Optional policy topic or title. Omit to return all published topics."New value: +"Optional canonical policy topic. Choose an advertised enum value; omit for all policies or a broader question."
    • addedInput schema / properties / topic / enum
      Added value: +[
      +  "minimum-booking-hours",
      +  "cancellation-rescheduling",
      +  "no-show-backfill",
      +  "coi-additional-insured",
      +  "payment-terms",
      +  "background-checks",
      +  "order-confirmation",
      +  "quote-response",
      +  "offers"
      +]
  3. Changed5 schema fields changed
    • addedOutput schema / properties / policies / items / properties / cap_usd
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / policies / items / properties / code
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / policies / items / properties / discount_percent
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / policies / items / properties / expires
      Added value: +{
      +  "description": "Offer expiry date in YYYY-MM-DD format.",
      +  "format": "date",
      +  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
      +  "type": "string"
      +}
    • addedOutput schema / properties / policies / items / properties / scope
      Added value: +{
      +  "type": "string"
      +}
  4. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  5. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/openWorldHint=false, so safety is covered; the description adds substantial behavior beyond that: omitted topic returns everything, unknown topics return the available-topic list rather than erroring, alias inputs are tolerated, per-order terms are tagged confirm_with_coordinator, and the result is characterized as 'an operational summary, not a contract'. That is exactly the context an agent needs to interpret output safely.

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?

Front-loaded with purpose, then coverage list, then tagged examples and hints; the tag structure keeps a dense description scannable. Slightly long, and the 'narrow lexical aliases remain accepted' clause is a marginal edge-case detail, but every sentence carries actionable information.

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 zero-required-parameter, single-enum read tool with an output schema already present, the description covers everything an agent needs: when to call it, how to pick a topic, what happens with no topic or a bad topic, and how to treat provisional values. Nothing material is left to inference.

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% and the enum is fully described there, so the baseline is 3; the description earns extra credit by explaining the omit-for-all semantics, the alias tolerance not visible in the enum, and the fallback behavior for unknown values. The three example invocations concretely map natural questions to topic values.

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?

States a specific verb and resource ('Get TempGuru's published booking and procurement policies') and immediately enumerates the concrete subject matter it covers (minimums, cancellation, COIs, deposits, rush fees, background checks). No sibling tool deals with policy retrieval, so the scope is unambiguous against check_availability, get_plan, request_quote, etc.

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 routes usage: 'Use for real booking questions that otherwise require an email', which tells the agent when this tool substitutes for human contact. It also gives selection guidance for the topic parameter (advertised topic = one policy, omit = all) and warns never to infer a missing number. It stops short of naming an alternative tool for adjacent questions, so a 4 rather than 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.