Skip to main content
Glama
Sign In

freehire

by me.freehire
OverviewDiscussionsAdmin

Save my mock hosting settings

buddy_mock_settings_set
Destructive

Replace the person's mock-interview hosting settings as a whole: the time zone their schedule is in, the meeting link guests receive, the topics they offer, and whether hosting is paused. Returns the saved settings.

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": {
      "timezone": "<timezone>",
      "meeting_url": "<meeting_url>",
      "topics": "<topics>",
      "paused": "<paused>"
    },
    "name": "buddy_mock_settings_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
pausedYesTrue stops new bookings; existing mocks stay.
topicsYesTopics the person offers to interview on, at least one.
timezoneYesIANA time zone the schedule's HH:MM times are in.
meeting_urlYesThe https link guests join the call at.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description reinforces the key behavioral trait by stating the settings are replaced wholesale, implying prior values are overwritten. It also notes the return ('Returns the saved settings'), though it does not cover permissions or downstream effects on future bookings beyond what the schema says for 'paused'.

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 sentences, front-loaded with the full-replacement semantics and the field list, with the return behavior trailing. No filler wording.

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 four-required-parameter mutation tool with no output schema, the description adequately conveys scope, replacement semantics, and the returned value. A note on whether missing/old values are discarded or auth requirements would round it out, but nothing critical is missing for correct invocation.

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 description coverage is 100%, with each property already documenting its meaning (IANA timezone, https link, topic enum list, paused behavior), so the schema carries the burden. The description merely paraphrases the same four fields in prose and adds no format or constraint detail beyond it.

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 gives a specific verb ('Replace') and resource ('mock-interview hosting settings') and enumerates the four settings covered, so an agent can distinguish this from sibling scheduling tools like buddy_mock_schedule_set_weekly or buddy_mock_schedule_add_override. It stops short of naming any sibling explicitly, which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'as a whole' implicitly signals this is a full-replacement operation with no partial-update mode, which is useful usage context. However, it never says when to prefer this over the schedule tools, nor states prerequisites such as needing existing hosting setup or being a registered mock host.

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