Skip to main content
Glama
Sign In
Vicarius vRx MCP Server

Vicarius vRx MCP Server

by Space-C0wboy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

external_reference_external_references_search_by_objects

Retrieve external references associated with a given object using search parameters from, size, and q.

Instructions

external_reference_external_references · POST /externalReferenceExternalReferences/searchByObjects — Get object by connection. Required: from, size, q. Requires a JSON request body.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "external_reference_external_references_search_by_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNoquery param enabled (bool)
from_Noquery param from (int)
sizeNoquery param size (int)
qNoquery param q (str)
bodyNoJSON request body

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.6/5.0
Behavior2/5

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

No annotations provided. The description claims required parameters (from, size, q) and required JSON body, but the schema lists all parameters as optional, creating a contradiction. The behavior is not clearly disclosed beyond being a search.

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

Conciseness3/5

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

Short description but includes redundant tool name and path. Could be more concise and structured. The list of required params is helpful but contradicts schema.

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 5 parameters and no output schema or annotations, the description is incomplete. It lacks explanation of the JSON body, the concept of 'connection', return values, pagination, and error handling.

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?

Schema coverage is 100%, but descriptions are minimal (e.g., 'query param enabled (bool)'). The description adds value by highlighting required params, but this contradicts the schema. It does not explain the meaning of 'q' or 'enabled', only adding confusion.

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 states it is a search for objects by connection using POST, and lists required parameters. It distinguishes from the sibling 'external_reference_external_references_search_by_fields' by specifying 'by connection', but does not clarify what 'connection' means.

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?

No guidance on when to use this tool vs alternatives like the sibling search by fields. It mentions required parameters but lacks context for appropriate usage.

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

Deploy Server

Other Tools