Skip to main content
Glama
doitintl

DoiT MCP Server

Official
by doitintl

search_customers

Read-only

Search across all DoiT customers using filters like classification, cloud platforms, monthly spend, and more to find matching customers with summary and pagination.

Instructions

DoiT-internal (doer) tool: search across ALL DoiT customers by what they have — classification/kind, customer type, segment, tier package, domains, cloud asset platforms (AWS, GCP, Google Workspace, Office 365, Azure), Flexsave, standalone (direct self-serve) cloud assets, monthly cloud spend, invoiced spend over a month range, and active contracts. All provided conditions are AND-combined; within a list field the match is any-of. Returns matching customers with a summary and a nextPageToken for paging. Requires DoiT employee access (non-doers get an authorization error). Use this to FIND customers across the base; use other tools to drill into a specific customer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoMatch any of these customer types, e.g. 'procurement-only', 'product-only', 'procurement-and-product'.
domainsNoMatch customers whose primary or secondary domain is any of these.
segmentNoMatch any of these customer segments, e.g. 'Invest', 'Incubate', 'Accelerate'.
pageSizeNoMaximum customers to return per page (default 50, max 200).
pageTokenNoOpaque page token from a previous response's nextPageToken, to fetch the next page.
standaloneNoIf set, match customers that do (true) or do not (false) have at least one standalone (direct self-serve) cloud asset. true keeps standalone/hybrid customers, false keeps resold-only ones.
hasFlexsaveNoIf set, match customers that do (true) or do not (false) have Flexsave enabled on any cloud.
tierPackagesNoMatch customers subscribed to any of these tier packages, e.g. 'navigator', 'solve'.
assetPlatformsNoMatch customers that have at least one asset on any of these cloud platforms (g-suite = Google Workspace, office-365 = Microsoft 365).
classificationNoMatch customers in any of these classifications (the customer 'kind').
contractsActiveNoIf true, match only customers that have at least one active/expired contract.
invoicedToMonthNoEnd month (YYYY-MM) for the invoiced-total spend filter. Requires invoicedFromMonth.
invoicedMaxTotalNoMaximum summed invoice total over the invoiced month range.
invoicedMinTotalNoMinimum summed invoice total over the invoiced month range.
invoicedFromMonthNoStart month (YYYY-MM) for the authoritative invoiced-total spend filter. Requires invoicedToMonth.
maxMonthlyCloudSpendNoMaximum denormalized monthly cloud spend.
minMonthlyCloudSpendNoMinimum denormalized monthly cloud spend (cheap, from the customer record).
Behavior4/5

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

Annotations already indicate read-only (readOnlyHint=true) and non-destructive (destructiveHint=false). The description adds context: internal tool, AND-combined conditions, any-of within lists, pagination via nextPageToken, and authorization requirement. No contradiction.

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

Conciseness4/5

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

The description is a single paragraph but well-structured, starting with purpose, then listing fields, then explaining logic, pagination, auth, and usage guidance. It is comprehensive without being overly verbose.

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?

Given the complexity (17 optional params, no output schema), the description covers purpose, behavior, pagination, auth, and comparison to siblings. It mentions return value (summary + nextPageToken) but lacks details on error handling or rate limits, which are acceptable given annotations.

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 baseline is 3. The description does not add significant meaning beyond the detailed schema descriptions for each parameter; it restates categories but not extra semantics. The logic of AND-combination and any-of is behavioral, not parameter-specific.

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 it searches across ALL DoiT customers by specified attributes, with a specific verb ('search') and resource ('customers'). It distinguishes from siblings by advising to use other tools for drilling into a specific customer.

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 states when to use ('FIND customers across the base') and when not (non-doers get auth error), and suggests alternatives: 'use other tools to drill into a specific customer'.

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/doitintl/doit-mcp-server'

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