Skip to main content
Glama

crexi_read

Read the current Crexi page text plus numbered buttons, links, and fields to inspect listings. Scope the read to a single element when you only need that section.

Instructions

Read the current Crexi page: its text and numbered buttons, links and fields.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "crexi_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/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 burden, and it does disclose the return shape (page text plus numbered interactive elements), which is the most valuable behavioral fact here. It says nothing about read-only safety, output size limits, truncation, or how the numbering relates to the click/type tools, leaving real gaps for an unannotated tool.

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?

One sentence, front-loaded with the verb and target, with the returned content enumerated immediately after the colon. No filler and nothing buried.

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-optional-parameter read tool with no output schema, the description should and does characterize what is returned. It is nearly complete, missing only notes on limits/truncation and how the numbered elements feed the sibling click and type tools.

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% and the single optional 'element' parameter is documented in the schema as reading only inside that element. The description does not mention scoping or the element parameter at all, so it adds nothing beyond the schema; baseline 3 applies.

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?

"Read the current Crexi page" gives a specific verb and resource, and the colon list (text, numbered buttons, links, fields) tells the agent exactly what comes back. It doesn't explicitly contrast itself with the read-adjacent siblings such as crexi_status or crexi_open, so sibling differentiation is only implicit in "current page".

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 word "current" implies this operates on the already-loaded page rather than a URL, which is useful context, but there is no statement of when to prefer this over crexi_open, crexi_status or crexi_guide. Usage is inferable, not stated.

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