Skip to main content
Glama
veeemlab

@veeemlab/itglue-mcp

by veeemlab

itglue_search_organizations

Search IT Glue organizations with case-sensitive substring matching. Auto-retries with word and diacritic variants on zero results. Supports format options to reduce response size.

Instructions

Search IT Glue organizations. IT Glue's filter[name] is a case-sensitive substring match — not fuzzy. On a 0-hit response, the tool auto-retries with first-word and diacritic-stripped variants and reports which strategy worked via meta.search_strategy. For genuine fuzzy lookup with confidence scoring, use itglue_find_org_match.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNofilter[name] — case-sensitive substring (IT Glue limitation; tool falls back to first-word and diacritic-stripped variants on miss).
organizationTypeIdNofilter[organization_type_id]
organizationStatusIdNofilter[organization_status_id]
psaIntegrationTypeNofilter[psa_integration_type] (e.g. manually, connectwise-rest, autotask).
pageSizeNopage[size] — items per page (default IT Glue: 50, max 1000 for most endpoints).
pageNumberNopage[number] — 1-based page index.
formatOptionsNoReduce response size for token-sensitive callers. compact mode keeps id+type plus a small set of identifying attributes; fields[] picks specific attribute keys; omitEmpty strips null/empty values.
Behavior5/5

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

Discloses key behavioral traits: filter[name] is case-sensitive substring (not fuzzy), auto-retry with variants on zero hits, and reports search strategy via meta.search_strategy. Since no annotations exist, description fully carries the transparency burden.

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?

Two sentences plus a sibling reference. No filler, every sentence adds value. Front-loaded with purpose and key constraints.

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 a search tool with 7 parameters, nested object, and no output schema, the description covers purpose, key behavioral nuances, and alternatives. Could mention response structure, but meta field hint and fallback details compensate somewhat.

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 100% with detailed descriptions. The tool description adds context for the 'name' parameter (fallback behavior) and mentions meta.search_strategy, which is not in schema. For other parameters, it adds little beyond schema. Overall adds some value above baseline.

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?

Clearly states 'Search IT Glue organizations'. Distinguishes from sibling itglue_find_org_match by noting it provides fuzzy lookup with confidence scoring. Specific verb and resource, with clear differentiation.

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

Usage Guidelines5/5

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

Explicitly explains when to use (search with case-sensitive substring), and when not to use (for fuzzy lookup use itglue_find_org_match). Also details fallback behavior on zero hits, providing clear context.

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/veeemlab/itglue-mcp'

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