hicar-mcp

Official

by HICAR-Model

Overview Schema Source Related Servers Discussions Admin

Python

Local

read_source

Read HICAR source code by file path or symbol name. Specify a line range for targeted code retrieval.

Instructions

Read HICAR source by file path (repo-rooted, line range) or by symbol name. Requires HICAR_REPO (live mode).

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

Input Schema

Name	Required	Description	Default
`end`	No
`path`	No
`start`	No
`symbol`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 25, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses the two reading modes and the repository requirement, but does not address behavior with missing inputs, error handling, or whether operations are read-only.

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 consists of two sentences with no redundant information. It front-loads the core purpose and concisely adds a critical requirement.

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?

Given no output schema and no annotations, the description should provide more context about return format, error scenarios, and when to prefer this tool over siblings. The current coverage is adequate but not thorough.

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%, but the description adds context by explaining that path should be repo-rooted and start/end define a line range. However, it does not detail the meaning of 'symbol' or clarify the relationship between parameters.

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 clearly states the verb 'read', the resource 'HICAR source', and specifies two modes: by file path with line range or by symbol name. This differentiates it from sibling tools like code_search or get_doc.

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 mentions a prerequisite ('Requires HICAR_REPO (live mode)') but does not explicitly state when to use this tool versus alternatives, nor when not to use it.

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