Skip to main content
Glama

things_get_areas

Retrieve all areas from your Things 3 workspace to organize tasks and projects by category, with optional result limits for focused management.

Instructions

Get all areas

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_resultsNoLimit number of results returned (defaults to all if not specified)

Implementation Reference

  • src/tools/get.ts:52-55 (registration)
    Registration of the "things_get_areas" tool in the GetToolHandler definitions list.
      name: 'things_get_areas',
      description: 'Get all areas',
      schema: GetListSchema
    },
  • Handler logic for "things_get_areas", parsing the script output into a JSON response.
    case 'things_get_areas':
      result = { areas: parseAreaList(output) };
      break;
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. It doesn't indicate whether this requires authentication, if results are cached, or what data structure is returned despite the missing output schema.

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

Conciseness3/5

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

While brief at three words, the description is insufficiently front-loaded with actionable information. Extreme brevity here represents under-specification rather than efficient communication.

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

Completeness1/5

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

Critically fails to differentiate from sibling 'things_get_area' (singular vs plural). With no output schema and no annotations, the description should explain the return format and domain-specific meaning of 'areas,' but provides neither.

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?

The input schema has 100% description coverage for the single 'max_results' parameter, establishing the baseline score. The description adds no additional semantic context about the parameter's usage or implications.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get all areas' restates the tool name with minimal expansion. It fails to explain what constitutes an 'area' in the Things domain or distinguish this from the sibling tool 'things_get_area' (singular).

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

Usage Guidelines1/5

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

No guidance provided on when to use this versus 'things_get_area' or other list-fetching siblings. No mention of when to apply the 'max_results' parameter versus fetching all results.

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/hildersantos/things-mcp'

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