Skip to main content
Glama
Stefan39

mite

by Stefan39
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List projects

mite_list_projects
Read-only

Lists active or archived projects and returns their IDs and budget details, helping you look up project IDs to filter time entries or review budgets.

Instructions

Lists projects from mite, active ones or with archived: true the archived ones; use it to look up project ids for filters such as project_id in mite_list_time_entries, for budget usage use mite_report_budget. Returns id, name, customer, archived flag, note, budget and budget_type; budget is in the unit given by budget_type (minutes or cents), not hours or currency units. The whole list is returned at once without paging.

Input Schema

NameRequiredDescriptionDefault
archivedNotrue = list archived entries instead of the active ones, e.g. true. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.1
    • changedInput schema / properties / archived / description
      Previous value: -"true = list archived entries instead of the active ones."New value: +"true = list archived entries instead of the active ones, e.g. true. Default: false."
  2. First observedv1.0.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly and openWorld, so the safety profile is covered. The description adds genuinely non-obvious behavior: the full list is returned without paging, and `budget` is expressed in `budget_type` units rather than hours or currency. That is useful context beyond annotations, though pagination absence is stated only in passing.

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?

Front-loaded with the tool's identity and scope, then purpose routing, then return shape. Every sentence carries information an agent needs; nothing is redundant.

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

Completeness5/5

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

There is no output schema, but the description enumerates the returned fields and explains the `budget`/`budget_type` relationship. Combined with the no-paging note, an agent has enough to call and interpret the tool correctly.

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%, so the schema already documents the single `archived` parameter. The description still reinforces the default-vs-archived semantics in plain terms, marginally improving over the schema but not adding new syntax.

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?

States a specific verb and resource ('Lists projects from mite') and immediately names the scope switch (active vs. archived). It explicitly separates itself from `mite_report_budget`, so an agent can choose between the two without opening schemas.

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?

Gives a concrete use case (look up project ids for `project_id` filters in `mite_list_time_entries`) and an explicit exclusion with the correct alternative for budget usage (`mite_report_budget`). The when-to-use and when-not-to-use are both present.

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

Deploy Server

Other Tools