Skip to main content
Glama

get-todo-task

get-todo-task
Read-only

Read a Microsoft To Do task and retrieve its body content, checklist items, and linked resources. Expand related entities or fetch all pages for complete data.

Instructions

Read the properties and relationships of a todoTask object.

💡 TIP: Returns a single To Do task. NOTE: $select is NOT supported — do not pass select parameter, Graph returns RequestBroker--ParseUri (400). Use $expand=linkedResources to include linked email/resource. Returns body content (HTML format), checklist items, and linked resources.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
expandNoExpand related entities
selectNoComma-separated fields to return, e.g. id,subject,from,receivedDateTime
todoTaskIdYesPath parameter: todoTaskId
fetchAllPagesNoFollow @odata.nextLink and merge up to 100 pages into one response. Can return enormous payloads—only when the user explicitly needs a full export. Prefer a small $top first, then paginate or narrow with $filter/$search.
includeHeadersNoInclude response headers (including ETag) in the response metadata
todoTaskListIdYesPath parameter: todoTaskListId
excludeResponseNoExclude the full response body and only return success or failure indication
Behavior4/5

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

Annotations declare readOnlyHint=true, destructiveHint=false. Description adds significant behavioral context: $select not supported (with specific error), recommends $expand for linked resources, and outlines return content (body, checklist, linked resources). No contradiction.

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

Conciseness4/5

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

Two short paragraphs with front-loaded main purpose. Tip section is well-placed. Slightly informal with emoji, but efficient and clear.

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 7 parameters and no output schema, description covers essential operational details: unsupported select, useful expand, and expected return content. Sufficient for a read operation.

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%, baseline 3. Description adds value by clarifying that 'select' parameter is not supported and that 'expand' should be used to include linked resources. Provides meaningful semantics beyond schema alone.

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?

Description explicitly states the tool reads a single todoTask object, with specific verb 'Read' and resource 'todoTask object'. It distinguishes from sibling tools like list-todo-tasks (plural) and update-todo-task.

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?

Provides clear context with tip about unsupported $select and recommended $expand. Implicitly contrasts with list/update tools but lacks explicit when-not-to-use alternatives beyond sibling list.

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/Softeria/ms-365-mcp-server'

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