Skip to main content
Glama
moneyforward-i

Admina MCP Server

get_devices

Retrieve and filter organizational device lists using advanced search parameters, pagination, and sorting to manage inventory effectively.

Instructions

Get a list of devices for an organization using advanced search and filtering.

Key Features

  • Combine query parameters (pagination, sorting) with body parameters (filtering)

  • Support for text search, field-specific filters, and complex queries

  • Pagination with cursor-based navigation

Example Usage

Find first 5 devices for user with email "someone@gmail.com":

  • Query: limit=5

  • Body: {"searchTerm": "someone@gmail.com", "searchFields": ["people.primaryEmail"]}

Pro Tips

  • 1: Always make sure understand the definition of the fields (preset and custom fields) before using them.

  • 2: If user search devices by category: pc, phone or other, please use body.type to filter devices by category.

  • 3: Always to understand what are current sub types of the devices. If the user search information relate to sub types, Please use body.filters.["preset.subtype"] to filter devices by sub types.

  • 4: We don't really need to use searchFields parameter to the search results in all fields, only use it when the user search information relate to specific fields.

  • 5: If user want to filter devices by status, please use body.filters.["preset.status"].eq to filter devices by status.

  • 5.1: Unassigned devices status should be "in_stock" or "decommissioned".

  • 6: If user want to filter devices by preset fields or custom fields, please check the field.kind first, we only support date, number, dropdown kind of fields.

  • 6.1: If the field.kind is date, please use body.filters.["preset.field_name"].minDate or body.filters.["custom.attributeCode"].minDate and body.filters.["preset.field_name"].maxDate or body.filters.["custom.attributeCode"].maxDate to filter devices by date range.

  • 6.2: If the field.kind is number, please use body.filters.["preset.field_name"].minNumber or body.filters.["custom.attributeCode"].minNumber and body.filters.["preset.field_name"].maxNumber or body.filters.["custom.attributeCode"].maxNumber to filter devices by number range.

  • 6.3: If the preset field field.kind is dropdown, please use body.filters.["preset.field_name"].eq or body.filters.["custom.attributeCode"].eq to filter devices by dropdown value.

  • 7: Combine multiple filters examples: {"preset.status":{"eq":"active"},"preset.subtype":{"eq":"desktop_pc"},"custom.custom_xxx":{"eq":"1"},"custom.dt_13":{"minDate":"2025-12-23","maxDate":"2025-12-25"},"custom.drp_4":{"eq":"1"}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of items to return per page
cursorNoBase64-encoded cursor for pagination
sortByNoSort by field. Format: `<preset | custom>.<unique field name>` or `people.displayName`
sortOrderNoSort order for the results
expandsNoExpand other datasets when fetching devices
peopleIdNoFilter devices by the people ID assigned to them
typeNoFilter devices by device type
employeeStatusNoFilter devices by the employment status of the assigned person
searchTermNoSearch term to filter devices
searchFieldsNoArray of field names to search within when using searchTerm. Supports memo, people fields, preset fields, and custom fields
filtersNoAdvanced filters. Keys look like `preset.<unique field name>`. There are certain extra virtual fields, such as `$age`
Behavior4/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. It effectively describes key behaviors: combining query and body parameters, pagination with cursor-based navigation, and detailed filtering logic. It also mentions constraints like field kind support and status values. However, it lacks information on rate limits, authentication needs, or error handling, which are important for a tool with 11 parameters.

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?

The description is structured with sections like 'Key Features', 'Example Usage', and 'Pro Tips', which aids readability. However, it is overly verbose with repetitive tips (e.g., multiple points on filtering) and could be more front-loaded; the core purpose is clear early, but the detailed tips might bury essential information. Some sentences could be condensed for better efficiency.

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 tool's complexity (11 parameters, nested objects, no output schema, and no annotations), the description does a good job of covering usage scenarios, filtering logic, and examples. It compensates for the lack of output schema by illustrating expected inputs. However, it doesn't fully address all contextual gaps, such as error cases or performance considerations, which could be important for such an advanced tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, but the description adds significant value beyond the schema. It explains how to combine parameters (query vs. body), provides example usage with specific parameter combinations, and offers detailed 'Pro Tips' on using filters for categories, statuses, and field types. This goes well beyond the schema's technical definitions, making parameter usage clear and practical.

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

Purpose4/5

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

The description clearly states the tool's purpose: 'Get a list of devices for an organization using advanced search and filtering.' It specifies the verb ('Get') and resource ('devices for an organization'), and mentions advanced search/filtering capabilities. However, it doesn't explicitly differentiate from sibling tools like 'get_device_custom_fields' or 'get_people_accounts', which prevents a perfect score.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool through the 'Pro Tips' section, which offers specific scenarios (e.g., filtering by category, status, or field types). It implies usage for device listing with filtering, but doesn't explicitly state when NOT to use it or name alternatives among siblings, such as 'get_device_custom_fields' for metadata-only queries.

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/moneyforward-i/admina-mcp-server'

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