OpenAkashic

Search And Read Top OpenAkashic Note

search_and_read_top

One-shot search + read for small/low-context agents.

Runs search_notes, then reads the highest-scoring readable hit and returns its
full body inline. Saves a round-trip compared to search → read_note.
Falls back to semantic `hints` when there is no direct match.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	No	Filter by note kind: 'capsule', 'claim', 'evidence', etc.
`tags`	No	Filter by tags — all specified tags must be present
`query`	Yes	Search terms in plain language. Returns the top matching note's full body in one call.
`include_body`	No	Include the full markdown body of the top result (default true)
`include_related`	No	When true, depth-1 neighbors of top results are returned as context_neighbors.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the burden of disclosure. It transparently explains the internal process: runs search_notes, reads the highest-scoring readable hit, and falls back to semantic hints on no match. This covers the key behavioral traits, though it leaves some edge cases unaddressed.

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 compact and front-loaded, with three sentences that each convey essential information without waste.

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?

The description is complete for a tool with an output schema, covering the main flow, the fallback, and the round-trip benefit. It doesn't address edge cases like no results or unreadable hits, but the output schema likely covers the return shape.

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 coverage is 100%, so the baseline is 3. The description mentions 'full body' which aligns with include_body but adds little meaning beyond the schema's parameter descriptions.

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 tool's purpose: 'One-shot search + read' followed by a specific process. It distinguishes from siblings by explicitly contrasting with 'search → read_note' and stating it saves a round-trip.

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

Usage Guidelines4/5

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

The description gives clear context: 'for small/low-context agents' and explains the advantage over separate search and read calls. However, it does not explicitly state when not to use it or list alternative tools.

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

All OpenAkashic 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.