Skip to main content
Glama

adamamer20-paper-search-mcp-openai

by ai.smithery
OverviewDiscussionsAdmin

search_semantic

Search academic papers from Semantic Scholar.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNo
queryYes
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / max_results / title
      Removed value: -"Max Results"
    • changedInput schema / properties / max_results / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / year / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / year / default
      Removed value: -null
    • removedInput schema / properties / year / title
      Removed value: -"Year"
    • addedInput schema / properties / year / type
      Added value: +"string"
    • removedInput schema / title
      Removed value: -"search_semanticArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "search_semanticOutput",
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to specify what the search returns (e.g., metadata, abstracts, citation counts), pagination behavior, rate limits, or whether authentication is required. The term 'Search' implies a read operation but lacks critical behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single efficient sentence with no redundant words. However, given the high complexity (0% schema coverage, numerous siblings, no output schema), the extreme brevity constitutes under-specification rather than optimal conciseness.

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

Completeness2/5

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

Given three undocumented parameters (0% schema coverage), no output schema, no annotations, and a crowded sibling space with similar tools, the description is materially incomplete. It omits necessary context about parameter usage, return values, and tool selection criteria.

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

Parameters2/5

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

With 0% schema description coverage, the description must compensate but does not. It fails to document the 'year' parameter format, 'max_results' constraints, or 'query' syntax (e.g., boolean support). While 'Search' implies the existence of a query, it provides no semantic details for any of the three parameters.

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?

The description clearly states the verb (Search) and resource (academic papers from Semantic Scholar), which identifies the specific corpus. However, it fails to distinguish when to use this tool versus the generic 'search' sibling or other academic search tools like 'search_arxiv' or 'search_google_scholar'.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus the numerous sibling search tools (search_arxiv, search_pubmed, search_google_scholar, etc.) or the generic 'search' tool. There are no stated prerequisites or exclusions.

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

All adamamer20-paper-search-mcp-openai toolsInspect
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.

Resources