Skip to main content
Glama

sch_search

Search scholarly research papers and academic publications to find relevant studies and citations for research projects.

Instructions

Alias of sch.search

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYes
topNo
limitNo

Implementation Reference

  • Core handler function implementing academic search by aggregating arXiv, Crossref, and Wikipedia results.
    export async function schSearch(q: string, top = 5) {
      const [ax, cr, wiki] = await Promise.all([
        arxivSearch(q, top),
        crossrefSearch(q, top),
        wikiSearch(q, 'en', top)
      ]);
      return [...ax, ...cr, ...wiki].slice(0, top * 2);
    }
  • Zod schema for input parameters of sch_search: query 'q', optional 'top' and 'limit'.
    const schSearchShape = { q: z.string(), top: z.number().int().optional(), limit: z.number().int().optional() };
  • src/server.ts:167-173 (registration)
    MCP server registration for the 'sch_search' tool (alias), calling schSearch handler.
    server.tool('sch_search', 'Alias of sch.search',
      schSearchShape, OPEN,
      async ({ q, top, limit }) => {
        const res = await schSearch(q, top ?? limit ?? 5);
        return { content: [{ type: 'text', text: JSON.stringify(res) }] };
      }
    );
  • src/server.ts:160-166 (registration)
    Primary MCP server registration for the related 'sch.search' tool.
    server.tool('sch.search', 'Academic-first search (arXiv + Crossref + Wikipedia).',
      schSearchShape, OPEN,
      async ({ q, top, limit }) => {
        const res = await schSearch(q, top ?? limit ?? 5);
        return { content: [{ type: 'text', text: JSON.stringify(res) }] };
      }
    );
Behavior2/5

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

The description provides no behavioral information beyond the openWorldHint annotation. While the annotation indicates this tool can handle unknown queries, the description doesn't add any context about what 'sch' represents, what kind of data is being searched, performance characteristics, error conditions, or response formats. For a search tool with only one annotation, this leaves significant behavioral gaps.

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 maximally concise with a single, straightforward statement. There's no wasted language or unnecessary elaboration. While this conciseness comes at the cost of completeness, the description itself is efficiently structured without redundancy or fluff.

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

Completeness1/5

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

For a search tool with three parameters, no output schema, and minimal annotations, the description is completely inadequate. It doesn't explain what domain is being searched ('sch'), what the search returns, how results are structured, or any constraints. The openWorldHint annotation provides some context, but the description fails to build on this foundation, leaving the tool's functionality largely opaque.

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

Parameters1/5

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

With 0% schema description coverage for all three parameters (q, top, limit), the description carries the full burden of explaining parameter meanings but provides absolutely no information about them. It doesn't explain what 'q' should contain, what 'top' and 'limit' control, their relationships, or acceptable value ranges. This leaves all parameters completely undocumented.

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

Purpose1/5

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

The description 'Alias of sch.search' is a tautology that merely restates the tool name without explaining what the tool actually does. It provides no information about the verb (search) or resource (what 'sch' represents), nor does it differentiate this tool from its sibling 'sch.search' or other search tools in the list. This fails to communicate any meaningful purpose to an AI agent.

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

Usage Guidelines1/5

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

The description offers no guidance on when to use this tool versus alternatives. It doesn't explain why this alias exists alongside 'sch.search', when to choose one over the other, or how it relates to other search tools like 'web.search' or 'wiki.search'. Without any usage context, an AI agent cannot make informed decisions about tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/khanhs-234/tool4lm'

If you have feedback or need assistance with the MCP directory API, please join our Discord server