Skip to main content
Glama

Look up IT assets

asset_lookup
Read-onlyIdempotent

Locate company assets such as laptops, monitors, phones, printers, and licenses by tag, employee, type, status, or model text, with paginated results.

Instructions

Find laptops, monitors, phones, printers and licenses by asset tag, assigned employee, type, status or model text. Paginated. Requires role: viewer.

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": "asset_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
typeNo
limitNoMax items per page (default 10, max 50)
queryNo
cursorNoOpaque cursor from a previous page (next_cursor)
statusNo
assigned_toNoEmployee id, e.g. E004
warranty_expires_beforeNo

Output Schema

NameRequiredDescriptionDefault
totalYes
assetsYes
next_cursorYesPass as cursor to get the next page; null when done

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the burden is light. The description adds two genuinely non-obvious traits: the viewer-role authorization requirement and paginated result delivery. Return shape is not described, but an output schema exists and covers that.

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?

Three short, front-loaded sentences with no filler: what it finds, that results are paginated, and the auth prerequisite. Every sentence carries operational information.

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

Completeness4/5

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

For an 8-parameter, zero-required, read-only search with an output schema and rich annotations, the description supplies the essentials: object domain, filter dimensions, pagination, and access requirement. The one gap is the warranty-expiry filter, which is neither mentioned nor described in the schema.

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

Parameters4/5

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

Schema coverage is only 38%, yet the description compensates by mapping 'model text' to the otherwise-undocumented 'query' parameter and enumerating tag, assigned employee, type, and status as filter dimensions. It omits warranty_expires_before and cursor/limit semantics, so it is not fully complete.

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?

States a specific verb ('Find') and resource ('laptops, monitors, phones, printers and licenses') plus the filterable dimensions, so an agent can tell this is an asset-inventory search rather than an expense, oncall, or directory lookup. It does not explicitly name or contrast any alternative, which keeps it just below a 5.

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?

'Requires role: viewer' is a concrete precondition that helps the agent decide whether the call is viable, and 'Paginated' signals it is a listing operation. However, there is no guidance on how the listed filters combine (AND vs. OR) or when this tool is preferable to a sibling, leaving usage implicit.

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