Skip to main content
Glama

HireNimbus home services MCP

Get provider details

get_provider_details
Read-onlyIdempotent

Fetches a HireNimbus provider profile by slug. Does not require authentication. Inputs include slug and optional context. Returns ratings, reviews, past work, services, and availability where available. Read-only.

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": {
      "slug": "<slug>"
    },
    "name": "get_provider_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
contextNoOptional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / context / description
      Previous value: -"Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names, phones, emails, street addresses, IDs, or other PII. Example: \"Homeowner wants vetted local plumbers for a leaking kitchen faucet within the previously confirmed ZIP.\""New value: +"Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent."
  2. Changed7 schema fields changed
    • addedInput schema / properties / context / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / context / default
      Added value: +null
    • changedInput schema / properties / context / description
      Previous value: -"Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""New value: +"Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names, phones, emails, street addresses, IDs, or other PII. Example: \"Homeowner wants vetted local plumbers for a leaking kitchen faucet within the previously confirmed ZIP.\""
    • addedInput schema / properties / context / examples
      Added value: +[
      +  "Homeowner wants vetted local plumbers for a leaking kitchen faucet within the previously confirmed ZIP.",
      +  "Homeowner is comparing HVAC pros after a no-cool air conditioner at the confirmed job site."
      +]
    • addedInput schema / properties / context / title
      Added value: +"Context"
    • removedInput schema / properties / context / type
      Removed value: -"string"
    • changedInput schema / required
      Previous value: -[
      -  "slug",
      -  "context"
      -]New value: +[
      +  "slug"
      +]
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds real context: no authentication required and the shape of the returned profile (ratings, reviews, past work, services, availability). 'Read-only' merely restates the annotation, and coverage caveats ('where available') are a nice touch.

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 short sentences, front-loaded with the core action and scope, with no filler beyond the mildly redundant 'Read-only.' It could merge the inputs and returns clauses, but it reads efficiently.

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?

An output schema exists, so the brief return summary is a bonus rather than a necessity, and the auth note plus read-only/idempotent behavior covers the main operational questions. The remaining gap is nothing about slug format/where it comes from and no sibling disambiguation.

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 50%: 'context' is fully documented with examples in the schema, while 'slug' has no schema description. The sentence 'Inputs include slug and optional context' mostly restates the schema and only marginally clarifies slug by tying it to a provider profile; it adds no format or resolution guidance.

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?

States a specific verb+resource ('Fetches a HireNimbus provider profile by slug') and names the key identifier. It does not distinguish itself from near-siblings such as search_providers or get_provider_reviews, which also return review/rating data, so an agent must infer the boundary.

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?

'Does not require authentication' is a useful usage condition, and 'by slug' implies an already-known provider. But there is no explicit when-to-use guidance or named alternative (search_providers vs get_provider_reviews vs find_*), so selection is only implied.

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.