Skip to main content
Glama

manage-entity

Manage all Float entities including people, projects, tasks, clients, departments, roles, accounts, and statuses. Perform CRUD operations and specialized actions by specifying entity type and operation.

Instructions

Consolidated tool for managing all core Float entities (people, projects, tasks, clients, departments, roles, accounts, statuses). Supports all CRUD operations and specialized functions through a decision-tree approach. Use entity_type to specify the entity and operation to specify the action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe entity ID (people_id, project_id, task_id, client_id, department_id, role_id, account_id, or status_id)
nameNoName of the entity
pageNoPage number for pagination
colorNoColor (hex code)
emailNoEmail address
levelNoRole level
notesNoNotes or description
accessNoAccess level
activeNoFilter by active status (0=archived, 1=active)
avatarNoAvatar URL
budgetNoBudget amount
formatNoResponse format - either "json" or "xml"json
statusNoFilter by status
accountsNoArray of account updates for bulk operations
billableNoBillable flag (0=non-billable, 1=billable)
end_dateNoEnd date in YYYY-MM-DD format
per-pageNoNumber of items per page (max 200)
positionNoPosition for ordering
priorityNoPriority level
timezoneNoAccount timezone
client_idNoFilter by client ID (for projects)
job_titleNoJob title
operationYesThe operation to perform (list, get, create, update, delete, or specialized operations)
parent_idNoParent department ID
people_idNoFilter by person ID
task_typeNoTask type
tentativeNoTentative flag (0=confirmed, 1=tentative)
departmentNoFilter by department (for people)
is_defaultNoWhether this is the default status
permissionNoFilter roles by permission
project_idNoFilter by project ID
repeat_endNoRepeat end date
start_dateNoStart date in YYYY-MM-DD format
descriptionNoRole description
edit_rightsNoEdit rights
entity_typeYesThe type of entity to manage (people, projects, tasks, clients, departments, roles, accounts, statuses)
hourly_rateNoHourly rate
permissionsNoRole permissions
status_typeNoType of status
view_rightsNoView rights
account_typeNoAccount type
actual_hoursNoActual hours
non_billableNoNon-billable flag (0=billable, 1=non-billable)
repeat_stateNoRepeat state
department_idNoFilter by department ID
employee_typeNoEmployee type (1=full-time, 0=part-time)
is_system_roleNoSystem role flag (1=system, 0=custom)
people_type_idNoPeople type (1=employee, 2=contractor, 3=placeholder)
estimated_hoursNoEstimated hours
permission_nameNoPermission name to check
permissions_dataNoPermissions data for account management
role_permissionsNoRole permissions to update
default_status_idNoDefault status ID to set
default_hourly_rateNoDefault hourly rate
department_filter_idNoDepartment filter ID
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions 'decision-tree approach' but does not explain constraints, authentication, side effects, or how parameters interact. With 55 parameters and many operations, the lack of behavioral detail is a significant gap.

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?

The description is only two sentences and immediately conveys the tool's purpose and core parameters. Every sentence is useful, and there is no redundancy. It is well-structured and efficient.

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

Completeness2/5

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

Given the tool's complexity (55 parameters, 8 entity types, 19 operations, numerous siblings), the description is far too brief. It does not cover parameter dependencies, expected outputs, or how to combine parameters for specialized operations. The absence of an output schema exacerbates this lack of completeness.

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 all 55 parameters, so each property already has a description. The tool description only adds a high-level mention of entity_type and operation, not supplementing the schema details. Baseline 3 is appropriate as the schema carries the weight.

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 it is a consolidated tool for managing all core Float entities and supports CRUD and specialized operations. It specifies the two key parameters (entity_type, operation). However, it does not detail which operations are applicable to which entities, which may leave some ambiguity for the agent.

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

Usage Guidelines2/5

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

The description does not provide guidance on when to use this consolidated tool versus the many specific sibling tools (e.g., create-person, delete-client). It merely states it is 'consolidated' without explaining trade-offs or selection criteria. The agent is left to infer usage context.

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/asachs01/float-mcp'

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