Skip to main content
Glama

About My Daily Journeys

get_business_profile
Read-only

Who My Daily Journeys (MDJ) is, where it operates, what it sells, how buying works, how to contact Maya, and the human service envelope that sets it apart from booking alone.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_business_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and closed-world scope are covered without the description's help. The description adds useful content scope (contact path, human service envelope) that goes beyond annotations, but says nothing about response format, completeness guarantees, or whether the profile data can go stale.

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 dense sentence with no filler, and the core identity ('Who MDJ is') is front-loaded. Minor deduction for vague jargon like 'human service envelope' and 'sets it apart from booking alone', which reads as marketing rather than operational information.

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 zero-parameter, read-only profile lookup with no output schema, the description does the necessary work by enumerating what topics the response covers, which substitutes for a return-value spec. It could be a notch more complete by stating the response shape (structured object vs. prose) or that the data is static reference material.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to add; the baseline of 4 applies. Nothing in the description misrepresents the call signature.

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 enumerates the resource's contents concretely (who MDJ is, where it operates, what it sells, buying process, Maya's contact, service envelope), which makes the tool's subject unmistakable and separable from siblings like list_products or create_cart_mandate. It stops short of 5 because there is no verb framing ('returns...', 'retrieves...') and no explicit naming of a sibling it contrasts with.

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?

Usage is only implied: by listing buying mechanics and Maya's contact details, it hints the tool is for pre-purchase orientation and human escalation questions. There is no explicit when-to-use statement, no when-not-to-use, and no named alternative among check_destination_season, estimate_trip, or list_products.

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