MCC Solutions

Search the MCC store

search_store

Read-onlyIdempotent

Find MCC Solutions downloadable kits, templates, ebooks and coaching sessions by topic (for example: small claims, executor, landlord, payroll, resume). Returns names, prices in USD, what each includes, and the product page where the person buys it.

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

Input Schema

Name	Required	Description	Default
`query`	Yes	Topic or words to search for, e.g. 'executor new jersey'

Output Schema

Name	Required	Description	Default
`note`	No
`store`	No
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare this is a safe, read-only, idempotent, closed-world search, so the bar is lower. The description adds useful behavioral context by stating it returns names, prices in USD, what each includes, and the product page where purchase happens, which goes beyond the annotations.

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?

The description is two sentences with zero waste, front-loading the purpose and then the return details. The product-type list and topic examples are purposeful and easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity, a fully described single parameter, rich annotations, and an output schema, the description is complete enough. It explains what is searched, gives query examples, and summarizes what is returned, so an agent has what it needs to call it correctly.

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 description coverage is 100%, so the single query parameter is already well documented. The description adds topic examples (small claims, executor, landlord, etc.) that give the agent a better sense of query phrasing, but this is marginal value over the schema baseline.

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 states a specific verb ('Find') and resource ('MCC Solutions downloadable kits, templates, ebooks and coaching sessions') with concrete topical examples, making the tool's purpose clear. It does not explicitly distinguish itself from sibling search/list tools, which keeps it just below 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?

The description implies usage ('by topic') and gives examples of topics, which helps the agent know when to search. However, it provides no explicit when-to-use versus alternatives or exclusions, leaving some inference to the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All MCC Solutions tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?