mcp-infoblox

get_object_by_ref

Retrieve full details of any Infoblox object using its reference string.

Instructions

Get any Infoblox object by its reference string. Useful for retrieving full details of an object.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ref": "<ref>"
    },
    "name": "get_object_by_ref"
  }
}

Input Schema

Name	Required	Description	Default
`ref`	Yes	Object reference string (e.g., record:a/ZG5z..., network/ZG5z...)
`return_fields`	No	Comma-separated list of fields to return

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Mar 12, 2026

TDQS

A3.5/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. It mentions 'retrieving full details' but does not disclose any side effects, authentication requirements, error handling, or behavior when the reference is invalid.

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 two sentences with no wasted words. It is front-loaded with the core purpose and remains concise while covering the essential function.

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

Completeness3/5

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

Given the tool's simplicity and good schema coverage, the description is adequate but leaves gaps in behavioral context like error handling and response format. Could benefit from mentioning that the ref must be obtained from search results.

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

Parameters3/5

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

Schema coverage is 100%, so the baseline is 3. The description adds minimal value beyond the schema, providing examples for 'ref' but no additional semantic guidance for 'return_fields'.

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

Purpose5/5

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

The description clearly states the action ('Get'), the resource ('any Infoblox object'), and the method ('by its reference string'). It distinguishes from sibling tools, which are about creating, deleting, or searching objects.

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

Usage Guidelines3/5

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

The description notes it's 'useful for retrieving full details of an object' but does not explicitly state when not to use it or compare to alternatives like 'search' tools. Usage context is implied but not fully specified.

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