Skip to main content
Glama
Sign In

HireMe MCP

by io.github.djoudad292
OverviewDiscussionsAdmin

Submit a project brief

submit_project_brief

File a project brief on the client's behalf. Djaouad replies with a fixed quote within 24 hours. Use after confirming scope with the human.

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": {
      "name": "<name>",
      "contact": "<contact>",
      "project_type": "<project_type>"
    },
    "name": "submit_project_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesClient name
notesNoAnything else
budgetNoe.g. '$3.5k - $9k'. A $900 audit is the entry point.
contactYesEmail or WhatsApp number to reply to
featuresNoFeature list, optional
timelineNoe.g. 'ASAP', '2-4 weeks'
project_typeYesWhat should be built, e.g. 'AI support chatbot'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / budget / description
      Previous value: -"e.g. '$500-$2k'"New value: +"e.g. '$3.5k - $9k'. A $900 audit is the entry point."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the description only needs to add context. It does add genuinely useful behavior: a human ('Djaouad') replies with a fixed quote within 24 hours, implying an asynchronous, externally-handled follow-up. It does not warn that repeat calls create separate briefs (non-idempotent) or describe failure modes.

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?

Three short sentences with no filler; the core action is front-loaded, followed by the expected response and the usage condition in priority order.

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 no output schema, the description correctly supplies the missing return-side information (fixed quote within 24 hours) and the submission precondition. It is close to complete, though it omits what happens on duplicate submission and any auth/contact-channel constraints.

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%, so every one of the 7 parameters (including the budget entry-point hint and contact format) is already documented in the schema. The description adds no parameter-level detail, so the 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 ('File a project brief on the client's behalf') and is unambiguously the only submission/write tool among siblings that are all getters (get_next_slot, get_pricing, get_profile, search_projects). An agent can identify it 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 an explicit precondition and ordering: 'Use after confirming scope with the human.' That tells the agent when the tool is appropriate, but it names no alternatives or exclusion conditions (e.g., what to do instead if scope is unconfirmed or a quote already exists).

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

All HireMe MCP 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