Skip to main content
Glama

Oxbox Energy product catalogue

Search Oxbox Energy

search
Read-onlyIdempotent

Search the Oxbox Energy website: the home page and the Oxbox brochure (specifications, certifications, enclosure and installation details). Ask in plain words, e.g. "Oxbox capacity in kWh" or "Oxbox UL listing". Returns ids, titles and source links; read one with fetch.

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

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to look for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already establish that this is a safe, read-only, idempotent, closed-world operation, so the description does not need to argue safety. It does add useful context: the search is limited to two specific sources, and results come back as ids, titles and source links requiring a separate fetch. It does not cover result counts, ranking, or what happens when nothing matches.

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 the corpus scope front-loaded, then query phrasing, then the return shape and next step. No sentence is redundant or padding.

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?

There is no output schema, so the description correctly carries the burden of describing return values (ids, titles, source links) and it does. The remaining minor gap is result volume or paging behavior, which an agent might want to know before calling.

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?

Schema coverage is 100%, so the schema alone already documents the single query parameter. The description goes beyond it by prescribing natural-language phrasing and supplying two example queries that show the expected granularity, which is real added meaning.

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?

The description names a specific verb (Search) and resource (the Oxbox Energy website), then narrows the corpus to the home page and the Oxbox brochure with the topics they cover (specifications, certifications, enclosure and installation details). It also distinguishes itself from the fetch sibling by saying results should be read with fetch.

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?

It gives a concrete usage pattern for the tool's only parameter ("Ask in plain words") with two example queries, and it explicitly routes follow-up reading to fetch. It does not mention when to use a sibling such as find_series or get_documents instead, so the guidance is clear but not exhaustive.

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