Skip to main content
Glama
doitintl

DoiT MCP Server

Official
by doitintl
OverviewSchemaSourceRelated ServersScoreDiscussions(1)Admin
TypeScript
Remote

list_assets

Read-only

Browse cloud assets, subscriptions, and resources with pagination and partial name filtering. Find assets by name or filter criteria.

Instructions

Use this when the user wants to browse their cloud assets, subscriptions, or resources. Returns a paginated list of assets. Supports partial name filtering. Do NOT use this for cost analysis (use run_query) or checking invoices (use list_invoices).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoPartial name filter (case-insensitive). Returns only assets whose name contains this string.
filterNoAn expression for filtering the results. Uses key:[value] syntax, e.g. "type:g-suite". Multiple filters can be connected using a pipe |. Different keys result in AND; same key multiple times results in OR.
pageTokenNoPage token, returned by a previous call, to request the next page of results.
maxResultsNoThe maximum number of results to return in a single page. Defaults to 100. Maximum allowed value is 249.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to restate safety. It adds value by disclosing pagination and partial name filtering behavior. No contradictions. Could mention return format but not required.

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 clear sentences, front-loaded with purpose, no unnecessary words. Efficient and well-structured.

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 list tool with no output schema, the description covers purpose, exclusions, and pagination. It is sufficiently complete given the schema and annotations. Slight gap on return structure, but overall solid.

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 mentions partial name filtering, which adds context to the 'name' parameter, but otherwise does not elaborate on other parameters. Adequate but not exceptional.

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 to use this tool for browsing cloud assets, subscriptions, or resources. It specifies the verb 'browse' and the resource 'assets'. It also distinguishes from siblings by explicitly listing what not to use (cost analysis, invoices).

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 provides when-to-use (browsing assets) and when-not-to-use (cost analysis -> run_query, invoices -> list_invoices). This gives clear context and alternatives, satisfying the dimension fully.

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