Skip to main content
Glama
Sign In

freehire

by me.freehire
OverviewDiscussionsAdmin

Book a mock interview

buddy_mock_book

Book a 60-minute mock interview with a host, the person attending as guest. starts_at must be one of the host's open slots exactly (RFC 3339) and topic one of the topics that host offers. Returns the booked mock with the counterpart's handle and the meeting link. A guest may hold at most 3 upcoming mocks.

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": {
      "handle": "<handle>",
      "starts_at": "<starts_at>",
      "topic": "<topic>"
    },
    "name": "buddy_mock_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesOne of the host's topics.
handleYesThe host's buddy handle.
timezoneNoIANA time zone the times are shown in, e.g. Europe/Berlin. An unknown or missing zone falls back to UTC; the result names the zone it used.
starts_atYesThe slot's start, RFC 3339, exactly as listed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare the write/non-idempotent/non-destructive profile; the description adds real behavioral context beyond them — the 3-upcoming-mock quota per guest, exact-slot matching, and that the response includes the counterpart's handle and a meeting link. It doesn't cover failure modes (e.g., slot taken between lookup and booking), keeping it short of a 5.

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?

Four front-loaded sentences that each carry information (constraints, return shape, quota) with no filler. The appositive 'the person attending as guest' is slightly awkward but harmless.

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?

For a 4-parameter mutation tool with no output schema, the description covers inputs, constraints, quota, and return contents, and the timezone fallback is documented in the schema. Only the post-booking failure behavior is left unstated.

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%, so 'topic is one of the host's topics' and 'starts_at exactly as listed (RFC 3339)' are largely restatements of the property descriptions. The description reinforces the exact-match requirement but adds no format or syntax detail the schema lacks; 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?

States a specific verb and resource ('Book a 60-minute mock interview with a host') plus the actor roles (host vs guest), which separates it cleanly from siblings such as buddy_mock_list, buddy_mock_cancel, and buddy_mock_slots. An agent can tell what this does 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?

Gives concrete preconditions: starts_at must be an existing open slot of that host and topic must be one the host offers. It does not explicitly route the agent to buddy_mock_slots or buddy_mock_hosts to discover valid slots/topics, which is the main gap.

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

All freehire toolsInspect
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.

Resources