Search for academic authors and retrieve their papers on Semantic Scholar. Provide author name and optionally limit results (1-50) to get relevant publications.
Search for authors and their papers on Semantic Scholar
| Name | Required | Description | Default |
|---|---|---|---|
| authorName | Yes | Author name to search for | |
| maxResults | No | Maximum number of papers to return (1-50) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must cover behavioral traits. It does not mention rate limits, authentication, return format (e.g., returns list of authors with papers), or any side effects. The description is too brief to inform behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence is concise but may be underspecified. It lacks structure or front-loading of key details. Acceptable but could be improved.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has 2 parameters, no output schema, and no annotations. Description only says 'search for authors and their papers'. It does not explain what data is returned (e.g., author IDs, paper titles, affiliations) or any pagination behavior. Incomplete for effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% (both parameters have descriptions). Baseline is 3 as per rules. The description does not add additional meaning beyond what is in the schema, so no bonus.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it searches for authors and their papers on Semantic Scholar. The verb 'search' and resource 'authors and their papers' are specific, and it distinguishes from sibling tool 'search_semantic_scholar' which likely searches papers generally.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like search_semantic_scholar. The description does not specify prerequisites or context for use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/flyanima/open-search-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server