Skip to main content
Glama

El Trabajito directory

get_business

Read-onlyIdempotent

Full public profile of one worker or business: about, services, service area, how to contact them (phone, WhatsApp, email, website, social pages), payment methods, rating and a link to the page. Give the slug from search_businesses.

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_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe profile slug, exactly as returned by search_businesses or top_rated (for example "carlos-jimenez").
languageNoLanguage of the names and links in the answer (default es).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"The profile slug, exactly as returned by search_businesses or top_rated (for example \"carlos-jimenez\")."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the payload's breadth — contact channels, payment methods, rating, page link — which tells the agent this is a rich single-record fetch. It does not discuss failure modes for an unknown slug or rate limits.

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?

One compact sentence with a colon-delimited field list, followed by a one-line sourcing instruction — front-loaded and waste-free. The field enumeration is dense but each item carries decision value for the agent.

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 only two fully-documented parameters, rich annotations, and no output schema, the description's field list usefully substitutes for a missing return-value contract. Nothing essential to invoking it correctly is absent, though an unknown-slug error behavior would round it out.

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% and both parameters are documented in the schema, so the baseline is 3. The description reinforces slug provenance (comes from search_businesses) but adds nothing about the language parameter or slug formatting beyond the schema's own example.

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 resource — the full public profile of one worker or business — and enumerates the fields returned (about, services, service area, contacts, payment methods, rating, link). That enumeration distinguishes it from search_businesses (which produces slugs) and get_business_reviews, though it never explicitly says 'returns a single profile rather than a list'.

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?

'Give the slug from search_businesses' establishes the prerequisite and the intended two-step workflow (search first, then fetch), which is exactly the context an agent needs. It offers no when-not guidance or explicit alternatives, so it stops short of full routing guidance.

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.

Resources