Skip to main content
Glama
Sign In

Corey James portfolio

by ai.coreyjames
OverviewDiscussionsAdmin

search

Search the portfolio (connector-compatible): returns results with id, title and url. Use fetch with an id for the full document.

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
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the result shape (id, title, url) and the follow-up fetch pattern, which is helpful, but says nothing about matching semantics, result limits, pagination, or authentication.

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?

The description is short and front-loaded: it states the action and result fields first, then the fetch follow-up. 'Connector-compatible' is vague and does not earn much space, but overall there is little waste.

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

Completeness3/5

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

For a simple one-parameter search tool without an output schema, it covers the basic return shape and the next step. It remains incomplete because it does not resolve its overlap with 'search_portfolio' or explain what the query accepts, both of which matter given the sibling set.

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

Parameters2/5

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

Schema description coverage is 0% for the single required 'query' parameter. The description only implies that 'query' is a search string and adds no syntax, format, or connector-compatibility details, so it does not compensate for the missing schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

It states a specific verb and resource ('Search the portfolio') and lists returned fields, so the basic action is clear. However, the sibling list contains 'search_portfolio', and the description does nothing to distinguish this tool from that near-identical name, leaving the agent unsure which search to invoke.

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?

It gives one useful routing rule: use 'fetch' with an id for the full document. It does not say when to use this search versus 'search_portfolio', nor does it give exclusions or query constraints, so guidance is partial.

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

All Corey James portfolio toolsInspect
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