Skip to main content
Glama

search_passwords

Search for password entries in IT Glue by organization, name, category, URL, or username. Returns metadata only, not actual passwords.

Instructions

Search for password entries in IT Glue (returns metadata only, not actual passwords)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organization_idNoFilter by organization ID
nameNoFilter by password entry name (partial match)
password_category_idNoFilter by password category ID
urlNoFilter by URL
usernameNoFilter by username
page_sizeNoNumber of results per page (max 1000, default 50)
page_numberNoPage number to retrieve (default 1)
sortNoSort field (prefix with - for descending)
Behavior4/5

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

With no annotations, the description adds key behavioral context: it returns metadata, not actual passwords. This is valuable. However, it omits other behaviors like pagination or auth requirements.

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?

Single sentence that conveys the core purpose and a critical limitation. No wasted words.

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?

The description covers the essential behavior but lacks guidance on effective use (e.g., filtering, pagination) given the tool has 8 parameters and no output schema.

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 has 100% coverage, so baseline is 3. The description does not add additional meaning beyond the schema parameter descriptions.

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?

Description clearly states verb 'search' and specific resource 'password entries in IT Glue', and distinguishes itself from siblings like 'get_password' by noting it returns only metadata.

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?

Description implies when to use (to search for password entries) but does not explicitly state when not to use or provide alternative tool names like 'get_password' for retrieving actual passwords.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wyre-technology/itglue-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server