Skip to main content
Glama

life.ayushrai.site product MCP

search_public_facts

Read-only

Search public life.ayushrai.site pages by a short query and return matching published facts. Do not use this for private data.

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": {
      "query": "<query>"
    },
    "name": "search_public_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWords to match against public pages.

Output Schema

NameRequiredDescriptionDefault
textYesPlain-text public facts from life.ayushrai.site. Never secrets or invented metrics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "text": {
      +      "description": "Plain-text public facts from life.ayushrai.site. Never secrets or invented metrics.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "text"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds meaningful scope context beyond that: only public, published content is searchable, which bounds what results can appear. It says nothing about matching behavior, ranking, result limits, or what happens when nothing matches, and an output schema exists so return shape need not be covered.

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 short sentences, zero filler, with the core purpose front-loaded and the constraint placed second. Every sentence earns its place.

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 one-parameter read-only search with a full output schema and a readOnly annotation, the description covers purpose, scope, and the key exclusion. The only real gap is what matching semantics or result ordering the agent should expect, which is minor at this complexity.

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 the single query parameter is documented as 'Words to match against public pages.' The description only adds the qualifier 'short query,' a minor hint about input size that the schema does not state. Baseline 3 is appropriate since the schema carries nearly all the semantics.

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 and resource: 'Search public life.ayushrai.site pages ... return matching published facts.' That is far more precise than a tautology, and the word 'public' plus 'published facts' naturally separates it from siblings like get_contact and get_profile. It stops short of an explicit sibling contrast, so a 4 rather than 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?

There is one explicit exclusion, 'Do not use this for private data,' which is genuinely useful routing guidance. However, no positive when-to-use condition is stated and no alternative is named for the private-data case (e.g., get_contact or get_profile), so usage 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.