TempGuru Event Staffing

Get Booking and Procurement Policies

get_policies

Read-only

Get TempGuru's published booking and procurement policies, plus any currently published public offer. Use for real booking questions that otherwise require an email. Values not supported by canonical copy are explicitly marked confirm_with_coordinator with TODO-for-Megan; 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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`topic`	No	Optional canonical policy topic. Choose an advertised enum value; omit for all policies or a broader question.

Output Schema

TableJSON Schema

Name	Required	Description
`scope`	No
`status`	Yes
`message`	No
`updated`	No
`policies`	No
`requested`	No
`disclaimer`	No
`data_version`	No
`policy_found`	Yes	Discriminator. false means the requested topic is not published.
`todo_for_megan`	No
`available_topics`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 17, 2026

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"
+]

Changed5 schema fields changedAug 14, 2026

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"
+}
```

Changed2 schema fields changedJul 29, 2026

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"

AddedJul 15, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description goes well beyond the annotations by disclosing how unsupported values are marked, instructing agents to never infer missing numbers, noting that unknown topics return an available-topic list, and adding the interpretive caveat that the output is 'an operational summary, not a contract.' These are high-value behavioral details.

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?

Info is front-loaded with the core purpose first, followed by usage guidance and examples. Every sentence contributes context that affects invocation behavior, and the format with examples and hints is efficiently structured without padding.

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?

Given the single optional parameter, rich schema, and annotations, the description is fully complete for invocation. It covers what happens with omission, unknown topics, aliases, unsupported values, and how to treat the response. The output schema exists, so return-value details are not required here.

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 a baseline of 3 applies, but the description adds meaning beyond the enum by explaining that omitting the topic returns all policies or a broader answer, that aliases are accepted, and that unknown topics return the list of available topics. It also provides concrete examples.

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?

The description clearly identifies the resource (TempGuru's published booking and procurement policies plus public offers) and uses a specific verb ('get'). It sets the tool apart from sibling tools like get_cities or get_roles by specifying a uniquely policy-related resource and scope.

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?

The description explicitly says to 'Use for real booking questions that otherwise require an email,' which gives clear context for when to invoke it. It does not explicitly list exclusions or alternative sibling tools, but the guidance is strong and contextual.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TempGuru Event Staffing tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.