Skip to main content
Glama

Corey James portfolio

get_page

The record for one page by URL or path: title, result, systems, technologies, stats, lede, quote, evidence. For an agent role, its function and every specialist on it; for a specialist, who it is for and every role it serves; for a function, its roles.

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": {
      "url": "<url>"
    },
    "name": "get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does usefully disclose the returned field set and that relationships (roles, specialists, functions) are expanded, which compensates somewhat for the absent output schema. It never states that the operation is read-only, what happens when the URL or path does not resolve, or how large the expanded relationship payloads can be.

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 definition is short and front-loads the resource and returned fields. The second sentence is compressed to the point of obscurity, with three parallel but loosely defined page-type rules that cost more reading effort than the tokens they save.

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 one-parameter lookup with no output schema, listing the returned fields is the right instinct and largely covers what an agent needs to decide to call it. However, the page-type conditions (agent role / specialist / function) are presented without enough context to know how they affect the response, and no failure behavior is described.

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 0% for the single required parameter, so the description must add meaning — and it does, by clarifying that the input accepts either a full URL or a path, which the bare schema string does not convey. It stops short of specifying the accepted path format or whether partial URLs are tolerated.

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?

The description communicates that this retrieves the record for a single page and enumerates the fields returned (title, result, systems, technologies, stats, lede, quote, evidence), but the verb is implicit ("The record for one page") rather than stated as an action. The second sentence is a dense conditional clause about page types (agent role, specialist, function) that is hard to parse and does not differentiate this tool from siblings like fetch or search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit statement of when to use this tool versus alternatives such as fetch, search, who, or contact. The only usage signal is the implicit "by URL or path" lookup mode, leaving the agent to infer that this is the single-record detail fetcher and the others are list/search tools.

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