search_venuesSearch DBLP venues (conferences + journals).
| Name | Required | Description | Default |
|---|---|---|---|
| hits | No | 1-1000 (default 30) | |
| first | No | 0-based offset | |
| query | Yes | Venue name or acronym (e.g. "ICLR", "Nature") |
| Name | Required | Description | Default |
|---|---|---|---|
| result | No |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "query": "ICLR"
+ },
+ {
+ "hits": 50,
+ "query": "Nature Machine Intelligence"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "result": {
+ "properties": {
+ "completed": {
+ "description": "Completion timestamp",
+ "type": "number"
+ },
+ "hit": {
+ "description": "Array of venue results",
+ "items": {
+ "properties": {
+ "acronym": {
+ "description": "Venue acronym if available",
+ "type": "string"
+ },
+ "info": {
+ "description": "Venue info string",
+ "type": "string"
+ },
+ "name": {
+ "description": "Venue full name",
+ "type": "string"
+ },
+ "url": {
+ "description": "DBLP venue page URL",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "hits": {
+ "description": "Total number of venue results",
+ "type": "number"
+ },
+ "published": {
+ "description": "Number of results in this response",
+ "type": "number"
+ },
+ "start": {
+ "description": "0-based offset of first result",
+ "type": "number"
+ }
+ },
+ "type": "object"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that the tool searches both conferences and journals, which is useful context but does not disclose further behavioral traits beyond what annotations provide.
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?
The description is a single, front-loaded sentence with no wasted words. It efficiently conveys the tool's purpose.
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?
Given that the input schema fully describes parameters, annotations cover behavior, and an output schema exists, the description is mostly complete. It could mention that the tool supports partial matching or returns venue metadata, but it is adequate.
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%, so the schema already documents all parameters. The description does not add any additional meaning beyond what the schema provides, hence baseline score of 3.
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?
The description clearly states the verb (search), resource (DBLP venues), and scope (conferences + journals). It distinguishes from sibling tools like search_authors and search_publications.
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?
The description lacks explicit guidance on when to use this tool versus alternatives. The context implies it is for finding venue names or acronyms, but no when-not-to-use or alternative suggestions are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.